All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Packard <keithp@keithp.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: mesa-dev@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Mesa-dev] [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888
Date: Fri, 22 Nov 2013 03:01:49 -0800	[thread overview]
Message-ID: <86d2lsem3m.fsf@miki.keithp.com> (raw)
In-Reply-To: <20131122102632.GQ27344@phenom.ffwll.local>


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

Daniel Vetter <daniel@ffwll.ch> writes:

> Hm, where do we have the canonical source for all these fourcc codes? I'm
> asking since we have our own copy in the kernel as drm_fourcc.h, and that
> one is part of the userspace ABI since we use it to pass around
> framebuffer formats and format lists.

I think it's the kernel? I really don't know, as the whole notion of
fourcc codes seems crazy to me...

Feel free to steal this code and stick it in the kernel if you like.

> Just afraid to create long-term maintainance madness here with the
> kernel's iron thou-shalt-not-break-userspace-ever rule ... Not likely
> we'll ever accept srgb for framebuffers though.

Would suck to collide with something we do want though.

-- 
keith.packard@intel.com

[-- Attachment #1.2: Type: application/pgp-signature, Size: 827 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:[~2013-11-22 11:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  4:12 [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888 Keith Packard
2013-11-22 10:26 ` Daniel Vetter
2013-11-22 11:01   ` Keith Packard [this message]
2013-11-22 16:17     ` [Mesa-dev] " Daniel Vetter
2013-11-22 16:17       ` Daniel Vetter
2013-11-22 16:17       ` Daniel Vetter
2013-11-22 17:46       ` Ville Syrjälä
2013-11-22 17:46         ` Ville Syrjälä
2013-11-22 22:12       ` [Intel-gfx] " Kristian Høgsberg
2013-11-22 22:12         ` Kristian Høgsberg
2013-11-22 23:05         ` Ville Syrjälä
2013-11-22 23:05           ` Ville Syrjälä
2013-11-22 23:43           ` Keith Packard
2013-11-22 23:43             ` Keith Packard
2013-11-22 23:43             ` Keith Packard
2013-11-23  1:10             ` Ville Syrjälä
2013-11-23  1:10               ` Ville Syrjälä
2013-11-25 14:57               ` Geert Uytterhoeven
2013-11-25 14:57                 ` Geert Uytterhoeven
2013-11-25 14:57                 ` Geert Uytterhoeven
2013-11-22 23:36         ` [Intel-gfx] " Keith Packard
2013-11-22 23:36           ` Keith Packard
2013-11-22 23:36           ` [Intel-gfx] " Keith Packard
2013-11-25  8:57         ` [Intel-gfx] [Mesa-dev] " Daniel Vetter
2013-11-25  8:57           ` Daniel Vetter
2013-11-25  8:57           ` Daniel Vetter
2013-11-25 14:15           ` [Intel-gfx] " Ville Syrjälä
2013-11-25 14:15             ` Ville Syrjälä
2013-11-25 14:15             ` Ville Syrjälä
     [not found]         ` <16967_1385369810_529310D2_16967_15891_1_20131125085723.GW27344@phenom.ffwll.local>
2013-11-25 15:14           ` i830 watermark problems - status? Thomas Richter
2013-11-25 15:23             ` Daniel Vetter
     [not found]             ` <26487_1385392973_52936B4D_26487_126_1_20131125152331.GB27344@phenom.ffwll.local>
2013-11-25 15:55               ` Thomas Richter
2013-11-25 20:30                 ` Daniel Vetter
     [not found]                 ` <26487_1385411456_5293B380_26487_2367_1_CAKMK7uFFZcf92XbzA9Mj2c0fdhDWZMKkZVNK9yy8Shc8pcLygg@mail.gmail.com>
2013-11-30 20:11                   ` Thomas Richter
2013-12-19 14:01                   ` intel-drm-nightly: hang and black screen on i830 Thomas Richter
2013-11-25 22:08 ` [PATCH] dri3, i915, i965: Add __DRI_IMAGE_FOURCC_SARGB8888 Eric Anholt
2013-12-13 22:58 ` Kenneth Graunke
2013-12-14  0:37   ` [Mesa-dev] " Keith Packard

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=86d2lsem3m.fsf@miki.keithp.com \
    --to=keithp@keithp.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mesa-dev@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 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.