From owner-mint@fishpool.com Sun Mar 23 03:13:36 2003 Message-ID: <3E7D15E6.18333932@chello.nl> Date: Sun, 23 Mar 2003 03:03:18 +0100 From: Henk Robbers X-Mailer: Mozilla 4.72 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] [CVS] Xaaes in freemint module References: <20030322214907.2018e1df.mandin.patrice@wanadoo.fr> <20030322144950.A2659@verin.klockars.net> <1048371955.3182.45.camel@joy.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: h.robbers@chello.nl Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: Petr Stehlik wrote: > > On So, 2003-03-22 at 14:49, Johan Klockars wrote: > > > No, it depend at the moment on some kernel source. It's also planned from > > > me to integrate XaAES much better with FreeMiNT. So it's part of the > > > > IMO, that is a really bad idea. But that might just be me. > > ?? XaAES does not work without FreeMiNT so why not integrate it better? > It's not like fVDI which runs also with TOS and MagiC. > Agreed. The traphandler really belongs to the kernel and then the moose. The parts that run in superviser mode. Perhaps the use of the pipes can be replaced by a dedicated AES API. That is, if you want to maintain the seperate AESSYS process. A efficiency increase of 100% should be possible. Sensitivity to mouse and keyboard can benefit hugely. MiNT + XaAES are very small by modern standarda. I have no objection against integrating XaAES completely in FreeMiNT. I can see AES functions run as kernel threads. Integration doesnt mean that you cannot have separate programs, nor that any modualarity will disappear. I trust Frank that the possibility of producing MiNT without XaAES (and the opposite) will always be possible. The MiNT side and the GEM side are pretty easy identifiable. If those partss arent messed up you will always have a bunch of AES function execution procedures by hand for porting to other systems. Tighter connection with the kernel might perhaps alleviate some of the problems the AES presents to virtual memory. Just some thoughts (Not pretending to be a kernel expert ;-). -- Groeten; Regards. Henk Robbers. mailto:h.robbers@chello.nl http://members.ams.chello.nl/h.robbers/Home.html Interactive disassembler: TT-Digger; http://digger.atari.org A GEM replacement for MiNT: XaAES; http://xaaes.atari.org A Home Cooked teXt editor: AHCX The free desktop: TERADESK