[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1492791271.25675.57.camel@redhat.com>
Date: Fri, 21 Apr 2017 18:14:31 +0200
From: Gerd Hoffmann <kraxel@...hat.com>
To: Christian König <christian.koenig@....com>
Cc: Ville Syrjälä
<ville.syrjala@...ux.intel.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
David Airlie <airlied@...ux.ie>,
Michel Dänzer <michel@...nzer.net>,
open list <linux-kernel@...r.kernel.org>,
dri-devel@...ts.freedesktop.org,
Pekka Paalanen <ppaalanen@...il.com>,
Sean Paul <seanpaul@...omium.org>,
amd-gfx@...ts.freedesktop.org,
Alex Deucher <alexdeucher@...il.com>,
Daniel Vetter <daniel.vetter@...el.com>,
Ilia Mirkin <imirkin@...m.mit.edu>
Subject: Re: [PATCH] drm: fourcc byteorder: brings header file comments in
line with reality.
Hi,
> > My personal opinion is that formats in drm_fourcc.h should be
> > independent of the CPU byte order and the function
> > drm_mode_legacy_fb_format() and drivers depending on that incorrect
> > assumption be fixed instead.
>
> The problem is this isn't a kernel-internal thing any more. With the
> addition of the ADDFB2 ioctl the fourcc codes became part of the
> kernel/userspace abi ...
Ok, added some printk's to the ADDFB and ADDFB2 code paths and tested a
bit. Apparently pretty much all userspace still uses the ADDFB ioctl.
xorg (modesetting driver) does. gnome-shell in wayland mode does.
Seems the big transition to ADDFB2 didn't happen yet.
I guess that makes changing drm_mode_legacy_fb_format + drivers a
reasonable option ...
cheers,
Gerd
Powered by blists - more mailing lists