From mint-bounce@lists.fishpool.fi Thu Mar 6 15:23:41 2008 From: "Jo Even Skarstein" To: "MiNT email list" Subject: Re: [MiNT] XaAES maintainer? Date: Thu, 6 Mar 2008 20:29:45 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <47CFA02C.9080703@atari.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1914 Importance: Normal X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joska@online.no Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: > -----Original Message----- > From: mint-bounce@lists.fishpool.fi > [mailto:mint-bounce@lists.fishpool.fi]On Behalf Of Odd Skancke > > drivers, etc. can be runtime loaded/uloaded. This is a kernel service I > needed to go further with XaAES; Load on demand certain services like > resolution switching code, window renderers, themes etc. The development Ozk, would you mind if I called you one day regarding this? This might affect some stuff I'm working on myself. It's a long-term project and can benefit greatly from some enhancements in the AES - I'd like to discuss this with you before I proceed. > of this is not finished, but I do intend to continue some day. For the > past months I've been too busy on my spare time to work on this but > hopefully I will be able to continue during this year. It is extremely encouraging to hear that you've not left the scene completely :-) Both you and Frank means a lot to the FreeMiNT community, and finding someone to continue your high quality work on XaAES and the kernel would be next to impossible. > development is something I want to have a 'say' in :) One thing I can > say right now is that I do not want XaAES or the kernel sources to be > compilable using anything but GCC. There are too many pitfalls and the Sticking to one compiler and one set of libraries is a good idea. I'm not particularly fond of gcc - even on my Milan060 it's painfully slow and I really don't like working with it. But I'm not working on XaAES so I really don't mind :-) Jo Even