From: Ben Widawsky <ben@bwidawsk.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
"Kristian H . Kristensen" <hoegsberg@gmail.com>,
Daniel Stone <daniels@collabora.com>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/3] drm: Create a format/modifier blob
Date: Wed, 17 May 2017 17:00:17 -0700 [thread overview]
Message-ID: <20170518000015.GA2334@mail.bwidawsk.net> (raw)
In-Reply-To: <20170517113144.ozglswrn27doitqg@phenom.ffwll.local>
On 17-05-17 13:31:44, Daniel Vetter wrote:
>On Tue, May 16, 2017 at 02:19:12PM -0700, Ben Widawsky wrote:
>> On 17-05-03 17:08:27, Daniel Vetter wrote:
>> > On Tue, May 02, 2017 at 10:14:27PM -0700, Ben Widawsky wrote:
>> > > +struct drm_format_modifier_blob {
>> > > +#define FORMAT_BLOB_CURRENT 1
>> > > + /* Version of this blob format */
>> > > + u32 version;
>> > > +
>> > > + /* Flags */
>> > > + u32 flags;
>> > > +
>> > > + /* Number of fourcc formats supported */
>> > > + u32 count_formats;
>> > > +
>> > > + /* Where in this blob the formats exist (in bytes) */
>> > > + u32 formats_offset;
>> > > +
>> > > + /* Number of drm_format_modifiers */
>> > > + u32 count_modifiers;
>> > > +
>> > > + /* Where in this blob the modifiers exist (in bytes) */
>> > > + u32 modifiers_offset;
>> > > +
>> > > + /* u32 formats[] */
>> > > + /* struct drm_format_modifier modifiers[] */
>> > > +} __packed;
>> >
>> > The struct should be in the uapi header. Otherwise it won't show up in
>> > libdrm headers when following the proper process.
>> > -Daniel
>> >
>>
>> I don't agree that blobs are ever really part of the API, but it doesn't hurt to
>> move it... in other words, done.
>
>Userspace writes them, the kernel reads them (or maybe even the other way
>round). How exactly is a specific blob and its layout not part of uapi?
>Can you explain your reasoning here pls?
>-Daniel
The API says there is a blob. If we wanted the fields in the blob to be explicit
we'd make an API that has the exact structure.
--
Ben Widawsky, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-05-18 0:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 5:14 [PATCH 1/3] drm: Plumb modifiers through plane init Ben Widawsky
2017-05-03 5:14 ` [PATCH 2/3] drm: Create a format/modifier blob Ben Widawsky
2017-05-03 11:00 ` Brian Starkey
2017-05-03 11:47 ` Daniel Stone
2017-05-03 12:39 ` Brian Starkey
2017-05-03 12:51 ` Brian Starkey
2017-05-03 13:51 ` [Intel-gfx] " Daniel Stone
2017-05-03 14:03 ` Brian Starkey
2017-05-03 14:07 ` [Intel-gfx] " Daniel Stone
2017-05-03 14:17 ` Brian Starkey
2017-05-03 13:15 ` Liviu Dudau
2017-05-11 17:58 ` Ben Widawsky
2017-05-03 13:32 ` Emil Velikov
2017-05-03 15:08 ` Daniel Vetter
2017-05-16 21:19 ` [Intel-gfx] " Ben Widawsky
2017-05-17 11:31 ` Daniel Vetter
2017-05-17 15:12 ` Daniel Vetter
2017-05-18 0:00 ` Ben Widawsky [this message]
2017-05-18 0:38 ` Rob Clark
2017-05-18 0:42 ` [Intel-gfx] " Rob Clark
2017-05-04 9:28 ` Daniel Stone
2017-05-03 5:14 ` [PATCH 3/3] drm/i915: Add format modifiers for Intel Ben Widawsky
2017-05-03 5:30 ` ✓ Fi.CI.BAT: success for series starting with [1/3] drm: Plumb modifiers through plane init Patchwork
2017-05-03 10:34 ` [PATCH 1/3] " Liviu Dudau
2017-05-03 13:45 ` [Intel-gfx] " Daniel Stone
2017-05-03 14:07 ` Liviu Dudau
2017-05-03 14:14 ` Daniel Stone
2017-05-03 14:52 ` Liviu Dudau
2017-05-03 16:45 ` Daniel Vetter
2017-05-03 17:30 ` [Intel-gfx] " Liviu Dudau
2017-05-10 16:34 ` Ben Widawsky
2017-05-10 17:24 ` Liviu Dudau
2017-05-10 19:33 ` [Intel-gfx] " Ben Widawsky
2017-05-10 20:21 ` Liviu Dudau
2017-05-10 16:33 ` Ben Widawsky
2017-05-03 18:28 ` kbuild test robot
2017-05-03 18:48 ` kbuild test robot
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=20170518000015.GA2334@mail.bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=daniel@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hoegsberg@gmail.com \
--cc=intel-gfx@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