From: Daniel Vetter <daniel@ffwll.ch>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v3 3/3] drm: Allow simpledrm to setup its emulated FB as firmware provided
Date: Thu, 5 May 2022 14:58:59 +0200 [thread overview]
Message-ID: <YnPKE+6DE12IsOj4@phenom.ffwll.local> (raw)
In-Reply-To: <47d3a7f6-24f9-7d54-48bf-09ab9e40e2de@redhat.com>
On Thu, May 05, 2022 at 02:45:27PM +0200, Javier Martinez Canillas wrote:
> Hello Daniel,
>
> On 5/5/22 14:11, Daniel Vetter wrote:
>
> [snip]
>
> >>
> >> And while I agree with you that these midlayer flags are horrible, that is
> >> what any other fbdev that makes use of a firmware-provided framebuffer set,
> >> so simpledrm emulated fbdev shouldn't be the exception IMO.
> >
> > So we discussed this a pile more on irc, and at least my take is that
> > people who run simpledrm but want to combine that with fbdev drivers and
> > expect it to all work nicely we can probably ignore. At least until all
> > this sysfb stuff is nicely unified, and at that point we shouldn't need
> > special flags anymore.
>
> I'm OK with this take and happy to just drop this patch-set then. My worry
> was just that someone could complain that we broke their uncommon setup [0].
>
> [0]: https://xkcd.com/1172/.
Since you have to explicitly enable simpledrm and that combo never
worked, we did not actually break anything.
Me, who has over a decade experience legalesing around the "no regression"
rule :-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/3] drm: Allow simpledrm to setup its emulated FB as firmware provided
Date: Thu, 5 May 2022 14:58:59 +0200 [thread overview]
Message-ID: <YnPKE+6DE12IsOj4@phenom.ffwll.local> (raw)
In-Reply-To: <47d3a7f6-24f9-7d54-48bf-09ab9e40e2de@redhat.com>
On Thu, May 05, 2022 at 02:45:27PM +0200, Javier Martinez Canillas wrote:
> Hello Daniel,
>
> On 5/5/22 14:11, Daniel Vetter wrote:
>
> [snip]
>
> >>
> >> And while I agree with you that these midlayer flags are horrible, that is
> >> what any other fbdev that makes use of a firmware-provided framebuffer set,
> >> so simpledrm emulated fbdev shouldn't be the exception IMO.
> >
> > So we discussed this a pile more on irc, and at least my take is that
> > people who run simpledrm but want to combine that with fbdev drivers and
> > expect it to all work nicely we can probably ignore. At least until all
> > this sysfb stuff is nicely unified, and at that point we shouldn't need
> > special flags anymore.
>
> I'm OK with this take and happy to just drop this patch-set then. My worry
> was just that someone could complain that we broke their uncommon setup [0].
>
> [0]: https://xkcd.com/1172/.
Since you have to explicitly enable simpledrm and that combo never
worked, we did not actually break anything.
Me, who has over a decade experience legalesing around the "no regression"
rule :-)
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2022-05-05 12:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 7:15 [PATCH v3 0/3] drm: Allow simpledrm to setup its emulated FB as firmware provided Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` [PATCH v3 1/3] drm: Remove superfluous arg when calling to drm_fbdev_generic_setup() Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` [PATCH v3 2/3] drm/fb-helper: Rename preferred_bpp drm_fbdev_generic_setup() parameter Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-03 17:02 ` Jernej Škrabec
2022-05-03 17:02 ` Jernej Škrabec
2022-05-03 17:02 ` Jernej Škrabec
2022-05-03 17:02 ` Jernej Škrabec
2022-05-03 17:02 ` Jernej Škrabec
2022-05-03 7:15 ` [PATCH v3 3/3] drm: Allow simpledrm to setup its emulated FB as firmware provided Javier Martinez Canillas
2022-05-03 7:15 ` Javier Martinez Canillas
2022-05-04 10:58 ` Daniel Vetter
2022-05-04 10:58 ` Daniel Vetter
2022-05-04 11:32 ` Javier Martinez Canillas
2022-05-05 12:11 ` Daniel Vetter
2022-05-05 12:11 ` Daniel Vetter
2022-05-05 12:45 ` Javier Martinez Canillas
2022-05-05 12:58 ` Daniel Vetter [this message]
2022-05-05 12:58 ` Daniel Vetter
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=YnPKE+6DE12IsOj4@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.