linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.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:30:36 +0000	[thread overview]
Message-ID: <53184E4C.1030408@ti.com> (raw)
In-Reply-To: <1394035969-32420-1-git-send-email-zonque@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On 06/03/14 12:18, Daniel Mack wrote:

>> 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.

Git should handle it fine, so it's not mandatory here. Still, I'd rather
have them via fbdev tree.

>> 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.

Well, there's drivers/gpu/. It sounds like a good match, and by "sounds"
I mean the word "gpu" sounds like a good match. I'm not sure if other
people have opinions on what drivers/gpu/ should contain, though.

 Tomi



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  parent reply	other threads:[~2014-03-06 10:30 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
2014-03-06 10:30 ` Tomi Valkeinen [this message]
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=53184E4C.1030408@ti.com \
    --to=tomi.valkeinen@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).