From: Daniel Mack <zonque@gmail.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH 0/4] Cleanups and fix for video/pxa3xx-gcu
Date: Thu, 06 Mar 2014 10:18:42 +0000 [thread overview]
Message-ID: <53184B82.4040006@gmail.com> (raw)
In-Reply-To: <1394035969-32420-1-git-send-email-zonque@gmail.com>
On 03/06/2014 10:23 AM, Tomi Valkeinen wrote:
> On 06/03/14 11:09, Daniel Mack wrote:
>> Given that this driver doesn't actually have any connection points to
>> the framebuffer or video subsystem (despite its location) maybe you can
>> just take these patches through your pxa tree? It's a PXA3xx specific
>> device, after all. Jean-Christophe, Tomi - any objections?
>>
>> The driver is also broken since awhile, and the fact that nobody noticed
>> tells me that our platform is most probably the only real user.
>
> If these do not have any dependencies to non-fbdev patches, and nothing
> else has dependencies to these patches, I'd rather take them via fbdev
> tree, based on the file location. There shouldn't be any conflicts, but
> just in case...
Ok for me. I really don't mind :)
> As a side note, I've got a drivers/video/ reorg patch series, possibly
> headed for v3.15, which moves the pxa3xx-gcu file to
> drivers/video/fbdev/.
Ah, ok. So then they really better go via your tree then.
> That's clearly not the right place for it, but I
> think it's easier to move it along the other files, and later move it
> back to drivers/video/.
Maybe it might be worth adding a subdirectory for hardware accelerators?
Because this is what the pxa3xx-gcu thing is all about really. And it's
only a tiny transport layer that passed commands between the hardware
block and a DirectFB userspace driver.
Thanks,
Daniel
next prev parent reply other threads:[~2014-03-06 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 16:12 [PATCH 0/4] Cleanups and fix for video/pxa3xx-gcu Daniel Mack
2014-03-06 2:09 ` Haojian Zhuang
2014-03-06 9:09 ` Daniel Mack
2014-03-06 9:15 ` Haojian Zhuang
2014-03-06 9:23 ` Tomi Valkeinen
2014-03-06 10:18 ` Daniel Mack [this message]
2014-03-06 10:30 ` Tomi Valkeinen
2014-03-06 10:53 ` Daniel Mack
2014-03-07 13:08 ` Tomi Valkeinen
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=53184B82.4040006@gmail.com \
--to=zonque@gmail.com \
--cc=linux-fbdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.