From: Hans de Goede <hdegoede@redhat.com>
To: Luke Jones <luke@ljones.dev>
Cc: platform-driver-x86@vger.kernel.org,
"Barnabás Pőcze" <pobrn@protonmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
linux-kernel@vger.kernel.org,
acpi4asus-user@lists.sourceforge.net, corentin.chary@gmail.com,
markgross@kernel.org, jdelvare@suse.com, linux@roeck-us.net
Subject: Re: [PATCH v2 0/1] platform/x86: asus-wmi: add support for ASUS screenpad
Date: Tue, 13 Jun 2023 12:27:56 +0200 [thread overview]
Message-ID: <5db606f4-c9ec-43a8-1c0d-16e1673668a7@redhat.com> (raw)
In-Reply-To: <5946924.lOV4Wx5bFT@fedora>
Hi,
On 6/7/23 00:45, Luke Jones wrote:
<snip>
>> I must admit I've lost track a bit of the state of v2 during this
>> discussion. Can I pick up v2 as is, or were there (other) remarks
>> which need addressing and should I expect a v3 ?
>
> There will be a V3. I don't anticipate any issues at all with this, and some
> folks have been using this patch with Gnome and KDE since V2 was submitted.
Ok.
>> ####### Switch to (off-topic) GPU mux discussion ########
> **snip**
>>>> I think the best thing to do here is to just use EFI on machines like
>>>> this. That or put grub in text mode so that it makes BIOS calls to
>>>> display text. Using GRUB_TERMINAL_OUTPUT=gfxterm combined with
>>>> classic BIOS booting will make grub try to directly drive the gfx
>>>> card itself and I'm not surprised that it gets that wrong in this
>>>> case.
>>>> Note I think that just using EFI is prefered over switching grub to
>>>> GRUB_TERMINAL_OUTPUT=console. I would expect
>>>> GRUB_TERMINAL_OUTPUT=console to also work but I'm not sure. I don't
>>>> think that the classic BIOS boot stuff is still tested by laptop
>>>> vendors and esp. not tested with non standard BIOS settings ...
>>>
>>> The grub gfx mode is GRUB_TERMINAL_OUTPUT="console", fedora default in
>>> all cases here. Grub itself shows fine when the MUX mode is in dgpu
>>> mode (aka, internal display connected to dgpu).
>>
>> Ah ok, so I misunderstood and the problem only happens *after* grub?
>>
>> Have I understood that correctly?
>>
>> And this is on Fedora with the nvidia binary driver ?
>>
>> The problem then likely is that the nvidia binary driver is not in
>> the initrd (which is by design since it may need to be rebuild on
>> a driver update while the kernel is kept at the same version,
>> so the initrd won't be rebuild).
>
> That was indeed the issue. It also creates new problems for when a user wants
> to use iGPU only via the plain (and frankly not adequate or good) method of
> simply removing the dGPU from the device tree.
>
> Currently I maintain the supergfxd tool which is a lot more advanced than the
> other gpu switchers around, and I expose both the above method, and also PCI
> hotplug, and the ASUS WMI method (which I now think is used by other vendors
> also). Hotplug and Asus method can force the device off, and it can't be
> brought back by a PCI rescan - but to do so safely the Nvidia drivers must be
> unused and unloaded. I guess I'll need to tweak the boot process of supergfxd
> and block things until this is done.
>
> Maybe we can move this to a new topic, because there looks to be a few things
> to discuss in relation to hybrid laptops, and specifically Nvidia with MUX,
> and Advanced Optimus.
Yes if you want to discuss this further please start a new mailinglist
thread for this and also please put the dri-devel list on the Cc:
dri-devel@lists.freedesktop.org
Regards,
Hans
prev parent reply other threads:[~2023-06-13 10:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 4:30 Luke D. Jones
2023-05-05 4:30 ` [PATCH v2 1/1] " Luke D. Jones
2023-05-05 13:08 ` Ilpo Järvinen
2023-05-05 23:43 ` Luke Jones
2023-05-06 1:30 ` Guenter Roeck
2023-05-06 3:48 ` Luke Jones
2023-05-06 4:43 ` Guenter Roeck
2023-05-06 8:09 ` Luke Jones
2023-05-06 13:24 ` Guenter Roeck
2023-05-08 8:21 ` Ilpo Järvinen
2023-05-06 11:52 ` [PATCH v2 0/1] " Hans de Goede
2023-05-15 12:39 ` Hans de Goede
2023-05-15 22:34 ` Luke Jones
2023-05-25 11:09 ` Hans de Goede
2023-06-04 4:52 ` Luke Jones
2023-06-06 8:58 ` Hans de Goede
2023-06-06 22:45 ` Luke Jones
2023-06-13 10:27 ` Hans de Goede [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=5db606f4-c9ec-43a8-1c0d-16e1673668a7@redhat.com \
--to=hdegoede@redhat.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luke@ljones.dev \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
/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®