From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
Aaron Plattner <aplattner@nvidia.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Alex Deucher <alexander.deucher@amd.com>,
Daniel Vetter <daniel.vetter@intel.com>,
Sam Ravnborg <sam@ravnborg.org>, Helge Deller <deller@gmx.de>
Subject: Re: [Intel-gfx] [PATCH 11/11] video/aperture: Only remove sysfb on the default vga pci device
Date: Thu, 12 Jan 2023 09:44:47 +0100 [thread overview]
Message-ID: <733eb41e-a296-47bb-ce06-18dff755723c@redhat.com> (raw)
In-Reply-To: <7b00e592-345f-4dd5-3452-7f6f70fc608a@suse.de>
On 1/12/23 08:55, Thomas Zimmermann wrote:
[...]
>> Thanks Daniel and Javier!
>>
>> I wasn't able to reproduce the original problem on my hybrid laptop
>> since it refuses to boot with the console on an external display, but I
>> was able to reproduce it by switching the configuration around: booting
>> with i915.modeset=0 and with an experimental version of nvidia-drm that
>> registers a framebuffer console. I verified that loading nvidia-drm
>
> Thank you for testing.
>
> One thing I'd like to note is that using DRM's fbdev emulation is the
> correct way to support a console. Nvidia-drm's current approach of
> utilizing efifb is fragile and requires workarounds from distributions
> (at least here at SUSE). Steps towards fbdev emulation are much appreciated.
>
I was meaning to mention the same. Fedora also is carrying a workaround just
for the Nvidia proprietary driver since all other drivers provide a emulated
fbdev device.
So getting this finally fixed will be indeed highly appreciated.
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-01-12 8:44 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 15:41 [Intel-gfx] [PATCH 01/11] drm/ast: Use drm_aperture_remove_conflicting_pci_framebuffers Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 02/11] drm/gma500: " Daniel Vetter
2023-01-12 9:04 ` Thomas Zimmermann
2023-01-12 9:59 ` Daniel Vetter
2023-01-12 10:24 ` Thomas Zimmermann
2023-01-12 10:45 ` Daniel Vetter
2023-01-12 12:15 ` Thomas Zimmermann
2023-01-12 15:32 ` Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 03/11] drm/aperture: Remove primary argument Daniel Vetter
2023-01-11 15:49 ` Thomas Zimmermann
2023-01-11 15:41 ` [Intel-gfx] [PATCH 04/11] video/aperture: use generic code to figure out the vga default device Daniel Vetter
2023-01-11 15:59 ` Thomas Zimmermann
2023-01-11 16:51 ` Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 05/11] video/aperture: Only kick vgacon when the pdev is decoding vga Daniel Vetter
2023-01-11 16:03 ` Thomas Zimmermann
2023-01-11 16:55 ` Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 06/11] staging/lynxfb: Use pci aperture helper Daniel Vetter
2023-01-11 16:05 ` Thomas Zimmermann
2023-01-11 15:41 ` [Intel-gfx] [PATCH 07/11] fbdev/radeon: use pci aperture helpers Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 08/11] fbdev/hyperv: " Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 09/11] video/aperture: Move vga handling to pci function Daniel Vetter
2023-01-11 15:41 ` [Intel-gfx] [PATCH 10/11] video/aperture: Drop primary argument Daniel Vetter
2023-01-11 16:09 ` Thomas Zimmermann
2023-01-11 15:41 ` [Intel-gfx] [PATCH 11/11] video/aperture: Only remove sysfb on the default vga pci device Daniel Vetter
2023-01-11 16:20 ` Thomas Zimmermann
2023-01-11 16:37 ` Daniel Vetter
2023-01-12 7:48 ` Thomas Zimmermann
2023-01-11 16:43 ` Javier Martinez Canillas
2023-01-11 16:58 ` Javier Martinez Canillas
2023-01-11 19:21 ` Aaron Plattner
2023-01-12 7:55 ` Thomas Zimmermann
2023-01-12 8:44 ` Javier Martinez Canillas [this message]
2023-01-11 15:48 ` [Intel-gfx] [PATCH 01/11] drm/ast: Use drm_aperture_remove_conflicting_pci_framebuffers Thomas Zimmermann
2023-01-11 17:02 ` Daniel Vetter
2023-01-11 16:10 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/11] " Patchwork
2023-01-11 16:38 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-01-12 9:41 ` [Intel-gfx] [PATCH 01/11] " Thomas Zimmermann
2023-04-04 14:45 ` Thomas Zimmermann
2023-04-18 0:53 ` Jammy Huang
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=733eb41e-a296-47bb-ce06-18dff755723c@redhat.com \
--to=javierm@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=aplattner@nvidia.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox