From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Javier Martinez Canillas <javierm@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/8] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers
Date: Wed, 5 Apr 2023 11:09:02 +0200 [thread overview]
Message-ID: <ZC06rmOFgBTd872G@phenom.ffwll.local> (raw)
In-Reply-To: <846e2048-cb7f-660c-6ec8-6f9c7b368187@suse.de>
On Wed, Apr 05, 2023 at 10:19:55AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 04.04.23 um 22:18 schrieb Daniel Vetter:
> > This one nukes all framebuffers, which is a bit much. In reality
> > gma500 is igpu and never shipped with anything discrete, so there should
> > not be any difference.
>
> I do own an Intel DN2800MT board with gma500 hardware. [1] It has a PCIe x1
> slot. I never tried, but in principle, there could be another graphics card
> in the system. The linked spec say 'Discrete: None'. I don't know what that
> means exactly.
Well even if that's the case, I'm not making the situation worse. Because
the old code also nuked everything. The new one at least only nukes the
vga if gma500 is decoding that, and not the the discrete card. In practice
it won't help, because I don't think you'll boot this in legacy vga mode
with vga16fb :-)
-Daniel
>
> Best regards
> Thomas
>
> [1] https://ark.intel.com/content/www/us/en/ark/products/56455/intel-desktop-board-dn2800mt.html
>
> >
> > v2: Unfortunately the framebuffer sits outside of the pci bars for
> > gma500, and so only using the pci helpers won't be enough. Otoh if we
> > only use non-pci helper, then we don't get the vga handling, and
> > subsequent refactoring to untangle these special cases won't work.
> >
> > It's not pretty, but the simplest fix (since gma500 really is the only
> > quirky pci driver like this we have) is to just have both calls.
> >
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
> > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > Cc: Javier Martinez Canillas <javierm@redhat.com>
> > ---
> > drivers/gpu/drm/gma500/psb_drv.c | 9 +++++++--
> > 1 file changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/gma500/psb_drv.c b/drivers/gpu/drm/gma500/psb_drv.c
> > index 2ce96b1b9c74..f1e0eed8fea4 100644
> > --- a/drivers/gpu/drm/gma500/psb_drv.c
> > +++ b/drivers/gpu/drm/gma500/psb_drv.c
> > @@ -422,12 +422,17 @@ static int psb_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> > /*
> > * We cannot yet easily find the framebuffer's location in memory. So
> > - * remove all framebuffers here.
> > + * remove all framebuffers here. Note that we still want the pci special
> > + * handling to kick out vgacon.
> > *
> > * TODO: Refactor psb_driver_load() to map vdc_reg earlier. Then we
> > * might be able to read the framebuffer range from the device.
> > */
> > - ret = drm_aperture_remove_framebuffers(true, &driver);
> > + ret = drm_aperture_remove_framebuffers(false, &driver);
> > + if (ret)
> > + return ret;
> > +
> > + ret = drm_aperture_remove_conflicting_pci_framebuffers(pdev, &driver);
> > if (ret)
> > return ret;
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Ivo Totev
--
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: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Javier Martinez Canillas <javierm@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 1/8] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers
Date: Wed, 5 Apr 2023 11:09:02 +0200 [thread overview]
Message-ID: <ZC06rmOFgBTd872G@phenom.ffwll.local> (raw)
In-Reply-To: <846e2048-cb7f-660c-6ec8-6f9c7b368187@suse.de>
On Wed, Apr 05, 2023 at 10:19:55AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 04.04.23 um 22:18 schrieb Daniel Vetter:
> > This one nukes all framebuffers, which is a bit much. In reality
> > gma500 is igpu and never shipped with anything discrete, so there should
> > not be any difference.
>
> I do own an Intel DN2800MT board with gma500 hardware. [1] It has a PCIe x1
> slot. I never tried, but in principle, there could be another graphics card
> in the system. The linked spec say 'Discrete: None'. I don't know what that
> means exactly.
Well even if that's the case, I'm not making the situation worse. Because
the old code also nuked everything. The new one at least only nukes the
vga if gma500 is decoding that, and not the the discrete card. In practice
it won't help, because I don't think you'll boot this in legacy vga mode
with vga16fb :-)
-Daniel
>
> Best regards
> Thomas
>
> [1] https://ark.intel.com/content/www/us/en/ark/products/56455/intel-desktop-board-dn2800mt.html
>
> >
> > v2: Unfortunately the framebuffer sits outside of the pci bars for
> > gma500, and so only using the pci helpers won't be enough. Otoh if we
> > only use non-pci helper, then we don't get the vga handling, and
> > subsequent refactoring to untangle these special cases won't work.
> >
> > It's not pretty, but the simplest fix (since gma500 really is the only
> > quirky pci driver like this we have) is to just have both calls.
> >
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> > Cc: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
> > Cc: Thomas Zimmermann <tzimmermann@suse.de>
> > Cc: Javier Martinez Canillas <javierm@redhat.com>
> > ---
> > drivers/gpu/drm/gma500/psb_drv.c | 9 +++++++--
> > 1 file changed, 7 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/gma500/psb_drv.c b/drivers/gpu/drm/gma500/psb_drv.c
> > index 2ce96b1b9c74..f1e0eed8fea4 100644
> > --- a/drivers/gpu/drm/gma500/psb_drv.c
> > +++ b/drivers/gpu/drm/gma500/psb_drv.c
> > @@ -422,12 +422,17 @@ static int psb_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent)
> > /*
> > * We cannot yet easily find the framebuffer's location in memory. So
> > - * remove all framebuffers here.
> > + * remove all framebuffers here. Note that we still want the pci special
> > + * handling to kick out vgacon.
> > *
> > * TODO: Refactor psb_driver_load() to map vdc_reg earlier. Then we
> > * might be able to read the framebuffer range from the device.
> > */
> > - ret = drm_aperture_remove_framebuffers(true, &driver);
> > + ret = drm_aperture_remove_framebuffers(false, &driver);
> > + if (ret)
> > + return ret;
> > +
> > + ret = drm_aperture_remove_conflicting_pci_framebuffers(pdev, &driver);
> > if (ret)
> > return ret;
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Ivo Totev
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2023-04-05 9:09 UTC|newest]
Thread overview: 112+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 20:18 [Intel-gfx] [PATCH 1/8] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` [Intel-gfx] [PATCH 2/8] video/aperture: use generic code to figure out the vga default device Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-05 11:27 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:27 ` Javier Martinez Canillas
2023-04-05 11:27 ` Javier Martinez Canillas
2023-04-04 20:18 ` [Intel-gfx] [PATCH 3/8] drm/aperture: Remove primary argument Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 21:20 ` [Intel-gfx] " Martin Blumenstingl
2023-04-04 21:20 ` Martin Blumenstingl
2023-04-04 21:20 ` Martin Blumenstingl
2023-04-04 21:20 ` Martin Blumenstingl
2023-04-04 21:20 ` Martin Blumenstingl
2023-04-05 9:25 ` [Intel-gfx] " Thierry Reding
2023-04-05 9:25 ` Thierry Reding
2023-04-05 9:25 ` Thierry Reding
2023-04-05 9:25 ` Thierry Reding
2023-04-05 9:25 ` Thierry Reding
2023-04-05 11:30 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:30 ` Javier Martinez Canillas
2023-04-05 11:30 ` Javier Martinez Canillas
2023-04-05 11:30 ` Javier Martinez Canillas
2023-04-05 11:30 ` Javier Martinez Canillas
2023-04-04 20:18 ` [Intel-gfx] [PATCH 4/8] video/aperture: Only kick vgacon when the pdev is decoding vga Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-05 11:31 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:31 ` Javier Martinez Canillas
2023-04-05 11:31 ` Javier Martinez Canillas
2023-04-04 20:18 ` [Intel-gfx] [PATCH 5/8] video/aperture: Move vga handling to pci function Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-05 11:34 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:34 ` Javier Martinez Canillas
2023-04-05 11:34 ` Javier Martinez Canillas
2023-04-04 20:18 ` [Intel-gfx] [PATCH 6/8] video/aperture: Drop primary argument Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-05 11:36 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:36 ` Javier Martinez Canillas
2023-04-05 11:36 ` Javier Martinez Canillas
2023-04-04 20:18 ` [Intel-gfx] [PATCH 7/8] video/aperture: Only remove sysfb on the default vga pci device Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-04 20:59 ` [Intel-gfx] " Aaron Plattner
2023-04-04 20:59 ` Aaron Plattner
2023-04-04 20:59 ` Aaron Plattner
2023-04-05 8:48 ` [Intel-gfx] " Daniel Vetter
2023-04-05 8:48 ` Daniel Vetter
2023-04-05 8:48 ` Daniel Vetter
2023-04-05 11:37 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:37 ` Javier Martinez Canillas
2023-04-05 11:37 ` Javier Martinez Canillas
2023-04-04 20:18 ` [Intel-gfx] [PATCH 8/8] fbdev: Simplify fb_is_primary_device for x86 Daniel Vetter
2023-04-04 20:18 ` Daniel Vetter
2023-04-05 11:40 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:40 ` Javier Martinez Canillas
2023-04-04 23:44 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/8] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers Patchwork
2023-04-04 23:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-04 23:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-05 7:49 ` [Intel-gfx] [PATCH 1/8] " Thomas Zimmermann
2023-04-05 7:49 ` Thomas Zimmermann
2023-04-05 8:05 ` [Intel-gfx] " Patrik Jakobsson
2023-04-05 8:05 ` Patrik Jakobsson
2023-04-05 8:15 ` [Intel-gfx] " Thomas Zimmermann
2023-04-05 8:15 ` Thomas Zimmermann
2023-04-05 8:07 ` [Intel-gfx] " Thomas Zimmermann
2023-04-05 8:07 ` Thomas Zimmermann
2023-04-05 8:59 ` [Intel-gfx] " Daniel Vetter
2023-04-05 8:59 ` Daniel Vetter
2023-04-05 9:26 ` [Intel-gfx] " Thomas Zimmermann
2023-04-05 9:26 ` Thomas Zimmermann
2023-04-05 9:38 ` [Intel-gfx] " Daniel Vetter
2023-04-05 9:38 ` Daniel Vetter
2023-04-05 11:00 ` [Intel-gfx] " Thomas Zimmermann
2023-04-05 11:00 ` Thomas Zimmermann
2023-04-05 11:16 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 11:16 ` Javier Martinez Canillas
2023-04-05 13:18 ` [Intel-gfx] " Daniel Vetter
2023-04-05 13:18 ` Daniel Vetter
2023-04-05 14:32 ` [Intel-gfx] " Thomas Zimmermann
2023-04-05 14:32 ` Thomas Zimmermann
2023-04-05 16:02 ` [Intel-gfx] " Daniel Vetter
2023-04-05 16:02 ` Daniel Vetter
2023-04-05 16:54 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 16:54 ` Javier Martinez Canillas
2023-04-05 17:14 ` [Intel-gfx] " Daniel Vetter
2023-04-05 17:14 ` Daniel Vetter
2023-04-05 17:43 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-05 17:43 ` Javier Martinez Canillas
2023-04-05 17:46 ` [Intel-gfx] " Patrik Jakobsson
2023-04-06 7:31 ` Daniel Vetter
2023-04-06 11:16 ` Patrik Jakobsson
2023-04-05 8:19 ` Thomas Zimmermann
2023-04-05 8:19 ` Thomas Zimmermann
2023-04-05 9:09 ` Daniel Vetter [this message]
2023-04-05 9:09 ` Daniel Vetter
2023-04-05 10:10 ` [Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/8] " Patchwork
2023-04-06 7:14 ` [Intel-gfx] [PATCH 1/8] " Thomas Zimmermann
2023-04-06 7:14 ` Thomas Zimmermann
2023-04-06 8:38 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-06 8:38 ` Javier Martinez Canillas
2023-04-06 8:49 ` [Intel-gfx] " Thomas Zimmermann
2023-04-06 8:49 ` Thomas Zimmermann
2023-04-06 9:05 ` [Intel-gfx] " Javier Martinez Canillas
2023-04-06 9:05 ` Javier Martinez Canillas
2023-04-06 9:05 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for series starting with [1/8] drm/gma500: Use drm_aperture_remove_conflicting_pci_framebuffers (rev2) Patchwork
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=ZC06rmOFgBTd872G@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=javierm@redhat.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 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.