From: Pekka Paalanen <ppaalanen@gmail.com>
To: "Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Ilia Mirkin <imirkin@alum.mit.edu>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [RFC][PATCH 0/2] drm: PATH prop for all connectors?
Date: Thu, 1 Aug 2019 12:51:09 +0300 [thread overview]
Message-ID: <20190801125109.2488a2d0@ferris.localdomain> (raw)
In-Reply-To: <97e2643d-c534-cfb5-bd27-4cf95c656104@amd.com>
[-- Attachment #1.1: Type: text/plain, Size: 672 bytes --]
On Tue, 16 Jul 2019 14:59:58 +0000
"Li, Sun peng (Leo)" <Sunpeng.Li@amd.com> wrote:
> On 2019-07-11 3:29 a.m., Pekka Paalanen wrote:
> > Wait, one can write udev rules for connectors and stuff?
> > How? What can they do?
>
> I was using it to generate user-friendly device names for the mst aux
> implementation:
> https://patchwork.freedesktop.org/patch/315900/?series=63237&rev=2
Hi,
what is that device node used for?
Are the "by-path" symlinks to help a display server associate the
right device node with the right DRM KMS connector resource?
The patch commit message did not explain what the names are
actually used for.
Thanks,
pq
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-01 9:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 18:43 [RFC][PATCH 0/2] drm: PATH prop for all connectors? Ville Syrjala
2019-06-13 18:43 ` [RFC][PATCH 1/2] drm: Improve PATH prop docs Ville Syrjala
2019-06-27 7:36 ` Pekka Paalanen
2019-06-13 18:43 ` [RFC][PATCH 2/2] drm/i915: Populate PATH prop for every connector Ville Syrjala
2019-06-27 7:37 ` Pekka Paalanen
2019-06-13 18:50 ` ✗ Fi.CI.CHECKPATCH: warning for drm: PATH prop for all connectors? Patchwork
2019-06-13 20:42 ` [RFC][PATCH 0/2] " Daniel Vetter
2019-06-27 7:35 ` Pekka Paalanen
2019-06-27 7:44 ` Michel Dänzer
2019-06-14 11:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-15 8:26 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-10 22:43 ` [Intel-gfx] [RFC][PATCH 0/2] " Lyude Paul
2019-07-11 7:20 ` Daniel Vetter
[not found] ` <20190711102923.3d219640@eldfell.localdomain>
2019-07-16 14:59 ` [Intel-gfx] " Li, Sun peng (Leo)
2019-08-01 9:51 ` Pekka Paalanen [this message]
2019-08-01 18:24 ` Li, Sun peng (Leo)
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=20190801125109.2488a2d0@ferris.localdomain \
--to=ppaalanen@gmail.com \
--cc=Sunpeng.Li@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--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