From mint-bounce@lists.fishpool.fi Fri Nov 27 12:51:18 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=72ylgJtQXKHGZut0eo8ZTm5Ywnv0oXMWK7uhPolS4Ek=; b=TrWQbOvMAqN/v8fKlrgQJlOZsbKojReppaoBKJwvCF3MTTPBCJS+3tn4bheduWeGaQ 9QmDibVXa67aYuPSZWAyGS6Ja/XCtPlX/5YFiP1ekbvX6FinimJWEOqzyWood0b3oopG X9mQftZgyd8n0OGGdl0I2Tn0sO8+7LBSdoMxY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HiRjKjfZAvmC12eaKmR/bj5yYRVrJHIlcxhAsur2nqruC/vtGb8ZRqieap+jIHjgGb 2i4b6OAL8htNGp+GmioS28cW80Lwu6RBGYYgBshaF5S2TIVfmIGEbb9VzwtsQrTJ8gdS NAnj3WuouJxsHSEpSdfac9TfCrlVR5Ci6VuZY= MIME-Version: 1.0 In-Reply-To: <11a6f2b10911270945k3d40974by62aeaa5d43c928c5@mail.gmail.com> References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <1259333803.8246.36.camel@petr> <7C3EA975C1884385A601809DA1F657B1@mercatus.local> <11a6f2b10911270833x5fbc85hdba1f96e1e70fcfe@mail.gmail.com> <4B1007F3.8090704@atari-source.org> <11a6f2b10911270945k3d40974by62aeaa5d43c928c5@mail.gmail.com> Date: Sat, 28 Nov 2009 04:48:42 +1100 Message-ID: <11a6f2b10911270948v54edd5ecp130d5555a61bb076@mail.gmail.com> Subject: [MiNT] Fwd: XaAES sources for FreeMiNT 1.16.3 From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Sat, Nov 28, 2009 at 4:10 AM, Mark Duckworth wrote: > I looked into this myself. For some reason the aranym pixel format > signature is different than XaAES is expecting. I would suspect this has > something to do with fvdi. My attempts to fix the issue with different fvdi > color combinations proved fruitless. But yeah I noticed this problem. What > I didn't know is that it ever worked before. > > Thanks, > Mark > yeah, its not fVDI, because when you place a new fVDI (or the one from AFROS) on PACK_3D nothing changes, 1.16.3 works fine with any newer version of fVDI. This confirms the fact that none of your fVDI changes had any affect. The only other thing I noticed was the the reported pixel format seemed "wierd" to me "E8E800". It made me wonder if EmuTOS had something to do with it, reporting what XaAES though to be "an invalid format". ALAN: cvs -r checkout -r branch-1_16 freemint Now I have the 1.16.3 sources (I presume) I can do some checking at source level, I have a hunch it may be a "motorola format" pixel that is expected, but it is getting an intel format, maybe, I wont know until I look, atm I'm just guessing, I honestly think its a lot simpler than that.. Paul