From: Emil Velikov <emil.l.velikov@gmail.com>
To: David Herrmann <dh.herrmann@gmail.com>
Cc: "Mark Kettenis" <kettenis@openbsd.org>,
"François Tigeot" <ftigeot@wolfpond.org>,
emil.l.velikov@gmail.com,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Thomas Klausner" <wiz@netbsd.org>,
"Robert Millan" <rmh@freebsd.org>,
"Konstantin Belousov" <kib@freebsd.org>
Subject: Re: [RFC PATCH 0/2] libdrm: Add master <> render node helpers
Date: Fri, 13 Feb 2015 09:18:01 +0000 [thread overview]
Message-ID: <54DDC149.5090108@gmail.com> (raw)
In-Reply-To: <CANq1E4SMWZPXYhwyrV7y2uxXwJGKvKBoTL+3S3tbZo_2TP0HJg@mail.gmail.com>
On 12/02/15 18:21, David Herrmann wrote:
> Hi
>
> On Tue, Feb 10, 2015 at 11:37 PM, Emil Velikov <emil.l.velikov@gmail.com> wrote:
>> On 02/02/15 00:14, Emil Velikov wrote:
>>> Hi all,
>>>
>>> As mentioned a couple of days ago at #dri-devel some(most) users of
>>> render nodes tend to rely on strict mapping between the primary and
>>> render node. I.e. something along the lines of
>>>
>>> fstat(render_fd, &sbuf);
>>> sprintf(primary_node, "/dev/dri/card%d",
>>> ((sbuf.st_rdev & 0x3f) | 0x80));
>>>
>>> Currently the following are (ab)using the above code:
>>> - xf86-video-nouveau
>>> - xf86-video-intel
>>> - libva (vaapi)
>>>
>>> As reminded by David Herrman, this is not the correct solution - thus
>>> I've added a couple of helpers which walk through sysfs of the
>>> respecitive device and return the correct device name.
>>>
>>> I'm not 100% happy with the function names, so suggestions are greatly
>>> appreciated. Any other comments are also welcome :)
>>>
>>> Note: BSD guys - you'll likely need your own version of these functions.
>>>
>> David, Daniel
>>
>> Can you please take a look at these two patches. Would be great if we
>> can minimize the above assumptions before they get too wide spread.
>
> The patches look ok. I really dislike the direct file-probing, though.
> I'd recommend using libudev or readdir_r() on /dev/dri/, but I'm not
> the one to ask about coding-style for libdrm, so fine with me.
>
Thanks for having a look. libudev is no used in libdrm so I will stay
away for now. I would prefer to use readdir on /dev/dri/ but AFAICT
there is no way to get the mapping from those alone. Am I missing
something ?
I'm also thinking that changing the prototypes, as below, might be
useful - i.e. return 0 on success, -ENODEV when the corresponding device
lacks render/primary device, and other negative value on error ?
char *drmGetRenderNameFromDeviceFD(int fd);
char *drmGetDeviceNameFromRenderFD(int fd);
int drmGetRenderNameFromDeviceFD(int fd, char **render);
int drmGetDeviceNameFromRenderFD(int fd, char **device);
Cheers,
Emil
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-02-13 9:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 0:14 [RFC PATCH 0/2] libdrm: Add master <> render node helpers Emil Velikov
2015-02-02 0:14 ` [PATCH 1/2] drm: add drmGet{Device, Render}NameFrom{Render, Device}Fd helpers Emil Velikov
2015-02-13 11:07 ` Frank Binns
2015-02-23 12:22 ` [PATCH libdrm v2] drm: add drmGet(Master|Render)NameFrom(Render|Master)FD functions Emil Velikov
2015-02-23 14:35 ` Frank Binns
2015-02-23 15:03 ` Emil Velikov
2015-03-07 0:58 ` [PATCH libdrm v3] " Emil Velikov
2015-03-07 1:08 ` Emil Velikov
2015-02-02 0:14 ` [PATCH 2/2] libdrm: add drmGetNodeType() helper Emil Velikov
2015-02-13 10:50 ` Frank Binns
2015-02-10 22:37 ` [RFC PATCH 0/2] libdrm: Add master <> render node helpers Emil Velikov
2015-02-10 23:32 ` Jonathan Gray
2015-02-12 18:21 ` David Herrmann
2015-02-13 9:18 ` Emil Velikov [this message]
2015-02-13 11:18 ` Frank Binns
2015-02-13 18:19 ` Emil Velikov
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=54DDC149.5090108@gmail.com \
--to=emil.l.velikov@gmail.com \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ftigeot@wolfpond.org \
--cc=kettenis@openbsd.org \
--cc=kib@freebsd.org \
--cc=rmh@freebsd.org \
--cc=wiz@netbsd.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.