From mint-bounce@lists.fishpool.fi Wed Jun 2 15:08:01 2010 Message-ID: <987169.45140356-sendEmail@descaro> From: "Helmut Karlowski" To: "Alan Hourihane" Cc: "helmut.karlowski@ish.de" Subject: Re: [MiNT] patch:MiNT:single-task Date: Wed, 2 Jun 2010 19:04:49 +0000 X-Mailer: sendEmail-1.55 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-534692.728965641" X-Antivirus: avast! (VPS 100602-1, 02.06.2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: helmut.karlowski@ish.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program. ------MIME delimiter for sendEmail-534692.728965641 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Alan Hourihane wrote: > On Wed, 2010-06-02 at 17:56 +0000, Helmut Karlowski wrote: > > Alan Hourihane wrote: > > > > Also there could come up problems when the bits 16,17 are set in p_flags > > and the kernel does not support ST-mode, because I suspect these are > > also used internally by MiNT for memory-protection-control. So at least > > the part that resets these bits should go into any kernel. > > Eh? Not sure I follow. If MP is using these bits they you'd need to find > some other bits regardless. I'm not using them - they just signal to the kernel and get translated into another variable, then reset. Anyway they could be set by mistake regardless of single-task etc. I'm not sure if it's easy to find a bit in p_flags that is not used by MiNT. The high-word of p_flags should always get zeroed when launching a prog IMHO. > But if you mean someone using the new XaAES with an older kernel would > break, then maybe you need to examine something in /kern to detect a > featureset available. As that could happen regardless of the #ifdef. It would just not work, and XaAES would not notice anything. So the only place to tell the user would be the kernel by ALERT or similar. > > Alan. > > PS. You seem to be removing the MiNT list from your replies, either that > or you are BCC'ing the MiNT list. You mean this: Alan Hourihane ? I thought it would be a real clever way to reply ;) It's done by my handmade macro-driven E-Mailer. Does it cause any problems? -Helmut ------MIME delimiter for sendEmail-534692.728965641--