From mint-bounce@lists.fishpool.fi Mon Jan 11 03:23:30 2010 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=stdcUUjL69zGnk+qHz91ZL+K88BYQ/8Fk6TInxRJAf0=; b=Hn4WUKYOBi1ILVpqPHvI50iEH7ZodhhjRKd49kqiCMACizZUTjIQX3K0qNiXw9Sp1w LYtVuM5bHNYm8EKK+3Dv4OHijiKFzvkpZ0hi7UTylEGG1J2j1CUz/fPwRSxOSM2hlwpu 0xYUq+QxM0CGZjVLbgolzHOJv5vtRT8LvXxrw= 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=yDzPda0dHY9OfvyJaXFRzXf2y54c8p5sg2IwmTXmCH49jsaV5HdpQKK2qZ/Y82XwPI quAyOYd8pQtHN2BUq8dTRXLKbqKle3EnHD8/Jk9BDeUTKW823puOQV0ZBVmpoo4wAkYN LlwK+JVxIQsPeXaTUxAemcxb6QFiVcqd5ABk4= MIME-Version: 1.0 In-Reply-To: <1262993346.16683.4159.camel@jetpack.demon.co.uk> References: <1262943873.16683.4110.camel@jetpack.demon.co.uk> <4B475C7C.3020600@charter.net> <11a6f2b11001081509o7ba202a4o6b5321115c5fbbf0@mail.gmail.com> <1262993346.16683.4159.camel@jetpack.demon.co.uk> Date: Mon, 11 Jan 2010 02:21:32 -0600 Message-ID: <11a6f2b11001110021hb88186fr52da3aa71a8ec869@mail.gmail.com> Subject: Re: [MiNT] FreeMiNT 1.17 Release plan 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 Fri, Jan 8, 2010 at 5:29 PM, Alan Hourihane wrote: > On Fri, 2010-01-08 at 17:09 -0600, Paul Wratt wrote: >> >> I do however need at least one of Helmuts fixes in main trunk for my >> additions to be usable, and that is his fix for the 1.17 XaAES pixel >> format problem. If that can be incorporated before the final >> enhancements trunk of Alan by the 15th, then there will be no problems >> in waiting for a full blown release around April, as I can drum up >> designers using the preliminary 15th+ CVS (where stable enough for GUI >> design work), and those efforts can bear fruit by the same point >> release, some of which may be suitable for CVS commit also, making it >> a bumper release all round.. > > I'm not sure which of Helmut's fixes really fix the problem, so if > Helmut or someone can suck that out I'll be sure to get that into the > main HEAD code asap. > > Alan. > I have noticed another thread where Falcon owners are now starting to see the "invalid pixel format issue", and if everything has gone well in the meantime, Helmuts branch is now compiling, and so I expect there to be some movement with this issue, which will allow the code to come to light, especially if its deeper that just XaAES, so I will still try get patches in within the next 2 days, but I expect it will take much longer to get the pixel format issue solved (unless a quick fix is used in the meantime, which will just continue to hide the bug itself, if indeed it is a bug) Paul