From mboxrd@z Thu Jan 1 00:00:00 1970 From: g.liakhovetski@gmx.de (Guennadi Liakhovetski) Date: Thu, 10 Sep 2009 14:15:27 +0200 (CEST) Subject: What's inside the pxa tree for this merge window In-Reply-To: <20090910115439.GU9410@buzzloop.caiaq.de> References: <20090910115439.GU9410@buzzloop.caiaq.de> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 10 Sep 2009, Daniel Mack wrote: > On Thu, Sep 10, 2009 at 07:46:26PM +0800, Eric Miao wrote: > > Daniel Mack (6): > > [ARM] pxa: add MFP_PULL_FLOAT > > [ARM] pxa: add clock definition for graphics controller > > [ARM] pxa: add device definition for graphics controller > > [ARM] pxa: rename GCU IRQ for consistency > > Regarding the PXA3xx GCU driver: > > I really wonder what's wrong with the fbdev people to ignore my very > simple patch for pxa3xx gcu enabling (not the gcu driver itself but just > the acceleration ID registration), even after the fifth (or so) > repost. I think, Andrew Morton is taking care of fbdev patches currently, try to ping him. > We've been using this driver for quite some time now. There's a small > bug hiding somewhere which we are currently trying to sort out, but > that's most probably not in the kernel driver but in the DirectFB part. > It would, however, be much easier for people to help testing if the > driver was upstream. > > Is there any way to push things a little? Except for that one bug, the > driver is a huge benefit for any PXA3xx application with graphical user > interface, so I'd really like to see it mainline. The sooner the better. Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/