From mint-bounce@lists.fishpool.fi Thu Jul 28 23:36:37 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] XAAES slow? From: Mark Duckworth To: Evan Langlois Cc: Odd Skancke , Mint List In-Reply-To: <1122493339.8675.6.camel@taro.coolrunningconcepts.com> References: <42B09A61.9020204@yahoo.fr> <1122498373.5660.523.camel@linuxbox> <1122492068.17747.40.camel@mduckworth.phillypark.net> <1122493339.8675.6.camel@taro.coolrunningconcepts.com> Content-Type: text/plain Date: Thu, 28 Jul 2005 17:32:37 -0400 Message-Id: <1122586358.20345.1848.camel@mduckworth.phillypark.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.1.fc4.nr) 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: mduckworth@atari-source.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: On Wed, 2005-07-27 at 14:42 -0500, Evan Langlois wrote: > On Wed, 2005-07-27 at 15:21 -0400, Mark Duckworth wrote: > > Yeah, > > > > I think what's in CVS right now is freaking great. Ozk, maybe we could > > make a new release for Xaaes.atariforge.net? It seems pretty stable and > > now we're starting to add experimental features... and it's crazy fast. > > Might be time to provide it to the people. And of course we should > > package up a mint cvs kernel with it since that seems to be necessary. > > This would be excellent. It would also be in time for the next aranym > release that seems to be coming up soon which should include a new afros > and it would be nice for the latest mint/XaAES to be included. > > Also, I want to see if the latest MiNT binary causes the same weird > issues the way I have things set up here, or if its just the compiler > differences that cause the odd crash. A known-working binary from the > same sources would test that. What do you guys think? Do you want me to pack up a Freemint/XaAES release? I think someone will have to branch it in CVS and then I can check it out and compile it. Please let me know as I can help out with this. We surely have to test the release on more platforms than probably have been so far. I have a TT, falcon and aranym. Thanks, Mark