From: g.liakhovetski@gmx.de (Guennadi Liakhovetski)
To: linux-arm-kernel@lists.infradead.org
Subject: What's inside the pxa tree for this merge window
Date: Thu, 10 Sep 2009 14:15:27 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0909101414340.4458@axis700.grange> (raw)
In-Reply-To: <20090910115439.GU9410@buzzloop.caiaq.de>
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/
next prev parent reply other threads:[~2009-09-10 12:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 11:46 What's inside the pxa tree for this merge window Eric Miao
2009-09-10 11:54 ` Daniel Mack
2009-09-10 12:15 ` Guennadi Liakhovetski [this message]
2009-09-10 12:23 ` Eric Miao
2009-09-10 12:32 ` Daniel Mack
2009-09-10 12:35 ` Eric Miao
2009-09-10 12:44 ` Daniel Mack
2009-09-10 13:05 ` Guennadi Liakhovetski
2009-09-10 13:09 ` Daniel Mack
2009-09-14 11:03 ` Guennadi Liakhovetski
2009-09-14 11:11 ` Russell King - ARM Linux
2009-09-15 6:30 ` Guennadi Liakhovetski
2009-09-15 6:50 ` Eric Miao
2009-09-15 7:34 ` Russell King - ARM Linux
2009-09-15 7:55 ` Guennadi Liakhovetski
2009-09-18 6:43 ` Matej Kenda
2009-09-18 6:47 ` Eric Miao
2009-09-18 7:45 ` Russell King - ARM Linux
2009-09-21 19:19 ` Guennadi Liakhovetski
2009-09-21 20:09 ` Russell King - ARM Linux
2009-09-21 20:32 ` Jamie Lokier
2009-09-30 12:09 ` arm tree in broken state (was Re: What's inside the pxa tree for this merge window) Pavel Machek
2009-09-30 12:16 ` Guennadi Liakhovetski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0909101414340.4458@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox