dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm: add an fb creation ioctl that takes a pixel format
Date: Fri, 11 Nov 2011 07:35:58 -0800	[thread overview]
Message-ID: <20111111073558.2f7abf78@jbarnes-desktop> (raw)
In-Reply-To: <CAPM=9txey-35BLdi=xR7E0wq_UwOf3EwJzaoUCEymndKjAvdHw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1462 bytes --]

On Fri, 11 Nov 2011 10:50:00 +0000
Dave Airlie <airlied@gmail.com> wrote:

> On Fri, Nov 11, 2011 at 10:47 AM, Dave Airlie <airlied@gmail.com> wrote:
> > On Tue, Nov 8, 2011 at 9:18 PM, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> >> To properly support the various plane formats supported by different
> >> hardware, the kernel must know the pixel format of a framebuffer object.
> >> So add a new ioctl taking a format argument corresponding to a fourcc
> >> name from videodev2.h.  Implement the fb creation hooks in terms of the
> >> new mode_fb_cmd2 using helpers where the old bpp/depth values are
> >> needed.
> >
> > I'm nearly sure I said this before, but please move the FOURCC defines
> > somewhere generic,
> > then use those, otherwise this is going to encourage crappy userspace
> > coding where
> > they drag in libv4l2 just to use a drm feature.
> >
> > I know they are generic, but userspace writes will start to include
> > v4l headers to get at
> > the same defines you use in the kernel.
> >
> 
> Oh and I'll take it as a follow-up patch. as I'd rather merge the base
> code now before it gets too late.

So just a separate header would be enough for you?
include/linux/fourcc or something?  Do you care if they continue to use
the v4l prefixes or not?  My preference would be to preserve that;
anything else is just churn for churn's sake.

Thanks,
-- 
Jesse Barnes, Intel Open Source Technology Center

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2011-11-11 15:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 21:18 [PATCH 1/2] drm: add plane support Jesse Barnes
2011-11-08 21:18 ` [PATCH 2/2] drm: add an fb creation ioctl that takes a pixel format Jesse Barnes
2011-11-09 13:25   ` InKi Dae
2011-11-09 14:08     ` Rob Clark
2011-11-10 14:54       ` InKi Dae
2011-11-10 16:30         ` Rob Clark
2011-11-12  9:14           ` InKi Dae
2011-11-11 10:47   ` Dave Airlie
2011-11-11 10:50     ` Dave Airlie
2011-11-11 15:35       ` Jesse Barnes [this message]
2011-11-11 10:56   ` Dave Airlie
2011-11-08 21:26 ` [PATCH 1/2] drm: add plane support Chris Wilson
2011-11-09 10:55 ` [PATCH 1/5] " Joonyoung Shim
  -- strict thread matches above, loose matches on Subject: below --
2011-11-08 17:38 [PATCH 1/2] " Jesse Barnes
2011-11-08 17:38 ` [PATCH 2/2] drm: add an fb creation ioctl that takes a pixel format Jesse Barnes

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=20111111073558.2f7abf78@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.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