From mint-bounce@lists.fishpool.fi Thu Mar 6 04:18:35 2008 Message-ID: <47CFA02C.9080703@atari.org> Date: Thu, 06 Mar 2008 08:41:32 +0100 From: Odd Skancke User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: MiNT email list Subject: Re: [MiNT] XaAES maintainer? References: , <00347025.01a6a8ca4b38@smtp.freeola.net>, <47CE8CCF.30321.460143@anodyne.cyberus.ca> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hi everybody, Peter Persson wrote: > My impression is that Ozk was working on a modular concept for the > kernel and the AES. Question is - in which state is Ozks current code - > what can be done to complete his work - how can we stimulate > collaboration and spawn further development? yes, this is true. I am working on laoding/unloading modules so that 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 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. > > 5 mar 2008 kl. 18.06 skrev Roger Burrows: > >> Hi everyone! >> With Ozk's departure from the Atari scene, is there a replacement >> official (or >> semi-official) maintainer for XaAES? [I have an ulterior motive of >> course - >> suggested changes :-)]. >> >> Roger Burrows Roger, I see no problems with you taking over the project, but I do want to follow and discuss your various ideas... XaAES and kernel 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 sources tend to get cluttererd up by ifdefs, making in harder than it must be to read. So, if it is OK with you to keep this a GCC only project, go ahead! :) Roger, Btw, just to refresh, my memory, what was these suggested changes? Best regards, Odd Skancke