Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640053
| Path | csiph.com!aioe.org!bofh.it!news.nic.it!robomod |
|---|---|
| From | Pavel Machek <pavel@ucw.cz> |
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality. |
| Date | Thu, 11 May 2017 23:30:01 +0200 |
| Message-ID | <tG3ON-3eu-1@gated-at.bofh.it> (permalink) |
| References | <tyBDY-39t-21@gated-at.bofh.it> <tyD34-45V-21@gated-at.bofh.it> <tyDw5-4fF-9@gated-at.bofh.it> <tyEBQ-55T-21@gated-at.bofh.it> |
| MIME-Version | 1.0 |
| Content-Type | multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" |
| Content-Disposition | inline |
| User-Agent | Mutt/1.5.23 (2014-03-12) |
| Sender | robomod@news.nic.it |
| List-ID | <linux-kernel.vger.kernel.org> |
| X-Mailing-List | linux-kernel@vger.kernel.org |
| Approved | robomod@news.nic.it |
| Lines | 74 |
| Organization | linux.* mail to news gateway |
| X-Original-Cc | Gerd Hoffmann <kraxel@redhat.com>, dri-devel@lists.freedesktop.org, Daniel Vetter <daniel.vetter@intel.com>, Pekka Paalanen <ppaalanen@gmail.com>, Ilia Mirkin <imirkin@alum.mit.edu>, Michel Dänzer <michel@daenzer.net>, Alex Deucher <alexdeucher@gmail.com>, amd-gfx@lists.freedesktop.org, Jani Nikula <jani.nikula@linux.intel.com>, Sean Paul <seanpaul@chromium.org>, David Airlie <airlied@linux.ie>, open list <linux-kernel@vger.kernel.org> |
| X-Original-Date | Thu, 11 May 2017 23:23:11 +0200 |
| X-Original-Message-ID | <20170511212311.GA6780@amd> |
| X-Original-References | <20170421075825.6307-1-kraxel@redhat.com> <20170421092530.GE30290@intel.com> <1492768218.25675.33.camel@redhat.com> <20170421110804.GH30290@intel.com> |
| X-Original-Sender | linux-kernel-owner@vger.kernel.org |
| Xref | csiph.com linux.kernel:1640053 |
Show key headers only | View raw
[Multipart message — attachments visible in raw view] - view raw
On Fri 2017-04-21 14:08:04, Ville Syrjälä wrote: > On Fri, Apr 21, 2017 at 11:50:18AM +0200, Gerd Hoffmann wrote: > > On Fr, 2017-04-21 at 12:25 +0300, Ville Syrjälä wrote: > > > On Fri, Apr 21, 2017 at 09:58:24AM +0200, Gerd Hoffmann wrote: > > > > While working on graphics support for virtual machines on ppc64 (which > > > > exists in both little and big endian variants) I've figured the comments > > > > for various drm fourcc formats in the header file don't match reality. > > > > > > > > Comments says the RGB formats are little endian, but in practice they > > > > are native endian. Look at the drm_mode_legacy_fb_format() helper. It > > > > maps -- for example -- bpp/depth 32/24 to DRM_FORMAT_XRGB8888, no matter > > > > whenever the machine is little endian or big endian. The users of this > > > > function (fbdev emulation, DRM_IOCTL_MODE_ADDFB) expect the framebuffer > > > > is native endian, not little endian. Most userspace also operates on > > > > native endian only. > > > > > > I'm not a fan of "native". Native to what? "CPU" or "host" is what I'd > > > call it. > > > > native == whatever the cpu is using. > > > > I personally find "native" more intuitive, but at the end of the day I > > don't mind much. If people prefer "host" over "native" I'll change it. > > "native" to me feels more like "native to the GPU" since these things > really are tied to the GPU not the CPU. That's also why I went with the > explicit endianness originally so that the driver could properly declare > what the GPU supports. You can easily have more than one GPU in the system. Plus these are used by cameras / frame grabbers, too. So anything else than CPU endianness is badly defined. (And I agree with the rest of the thread -- we should really be explicit; fourcc should specify what format the image data are in, and it should be possible to write fourcc + raw data into file and transfer it between machines.) Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Pavel Machek <pavel@ucw.cz> - 2017-05-11 23:30 +0200 Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality. Ville Syrjälä <ville.syrjala@linux.intel.com> - 2017-05-12 11:20 +0200
csiph-web