From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org,
Peter Robinson <pbrobinson@gmail.com>,
David Airlie <airlied@linux.ie>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/fb-helper: improve DRM fbdev emulation device names
Date: Tue, 25 May 2021 15:52:51 +0200 [thread overview]
Message-ID: <79f227c4-5ed6-23e8-2d74-3197871359f8@redhat.com> (raw)
In-Reply-To: <4e81ab57-a240-952a-7423-22dc830bc62f@suse.de>
Hello,
On 5/25/21 3:34 PM, Thomas Zimmermann wrote:
[snip]
>>
>> If you guys with your distro hats on all think it doesn't matter, then
>> yeah I'm all for dropping the somewhat silly -drm or drmfb suffixes. I
>> think that was just way back so it's easier to know you've loaded the
>> right driver, back when there was both drm and native fbdev drivers
>> around. But now I think for new hw there's only drm, so should be all
>> fine.
>
> Suse doesn't use fbdev, except for some outliers; most notably hypervfb
> and generic efifb/vesafb. Both are now being replaced with drm code.
> From what I've seen, it's the same for other distros. And X11 checks
> for the existence of device files anyway IIRC.
Yes, I believe is the same for us.
I'll post a patch to just remove the suffix then. Thanks you both
for the feedback.
>
> Best regards
> Thomas
>
>> -Daniel
>>
>
Best regards,
--
Javier Martinez Canillas
Software Engineer
New Platform Technologies Enablement team
RHEL Engineering
prev parent reply other threads:[~2021-05-25 13:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 13:19 Javier Martinez Canillas
2021-05-21 15:33 ` Daniel Vetter
2021-05-21 16:53 ` Thomas Zimmermann
2021-05-21 17:18 ` Javier Martinez Canillas
2021-05-21 18:53 ` Thomas Zimmermann
2021-05-25 13:08 ` Daniel Vetter
2021-05-25 13:34 ` Thomas Zimmermann
2021-05-25 13:52 ` Javier Martinez Canillas [this message]
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=79f227c4-5ed6-23e8-2d74-3197871359f8@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=pbrobinson@gmail.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®