From: Keith Packard <keithp@keithp.com>
To: "Kristian Høgsberg" <krh@bitplanet.net>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/gem: Add new flink_to ioctl
Date: Thu, 08 Jul 2010 08:59:00 -0700 [thread overview]
Message-ID: <yunfwzurmm3.fsf@aiko.keithp.com> (raw)
In-Reply-To: <1278602605-21728-1-git-send-email-krh@bitplanet.net>
[-- Attachment #1.1: Type: text/plain, Size: 673 bytes --]
On Thu, 8 Jul 2010 11:23:25 -0400, Kristian Høgsberg <krh@bitplanet.net> wrote:
> - a mechanism to attach a binary blob to an flink_to buffer name.
> open_with_data returns the data. Userspace (typically libdrm)
> decides the layout and versioning of the blob and the contents
> will be chipset specific. it's an opaque blob to the kernel,
> which doesn't need to know about stride and formats etc.
Arbitrary binary blobs considered harmful? Even if the kernel doesn't
need to know all of this data, having it in an explicit (versioned)
format will protect applications from randomly mis-interpreting the data.
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 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
next prev parent reply other threads:[~2010-07-08 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-08 15:23 [PATCH] drm/gem: Add new flink_to ioctl Kristian Høgsberg
2010-07-08 15:59 ` Keith Packard [this message]
2010-07-08 16:14 ` Kristian Høgsberg
2010-07-08 16:37 ` Chris Wilson
2010-07-08 16:49 ` Jesse Barnes
2010-07-08 17:21 ` Alan Cox
2010-07-08 18:15 ` Keith Packard
2010-07-08 18:48 ` Kristian Høgsberg
2010-07-08 22:15 ` Kristian Høgsberg
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=yunfwzurmm3.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=krh@bitplanet.net \
/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.