From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 218685] asus-nb-wmi fails to load due to conflict with amd-pmf
Date: Wed, 10 Apr 2024 11:35:13 +0000 [thread overview]
Message-ID: <bug-218685-215701-xzAe4xd3aT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218685-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=218685
--- Comment #28 from al0uette@outlook.com ---
(In reply to Mario Limonciello (AMD) from comment #23)
> It looks like the BIOS has a bug that it's advertisement of that bit even
> though it doesn't work.
> I guess in Windows this is a no-op.
>
> Hans - there's a few ways to handle this I can think of.
> 1. Quirk against this system and BIOS to ignore that bit in AMD PMF.
> 2. Allow multiple drivers to register for platform profile.
> 3. Do nothing, let Asus fix in BIOS.
>
> What do you want to do?
I really doubt whether ASUS will fix this BIOS bug. I contacted ASUS consumer
support today for the CPPC problem and they seem unwilling to provide Linux
support
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-04-10 11:35 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-218685-215701@https.bugzilla.kernel.org/>
2024-04-09 15:49 ` [Bug 218685] asus-nb-wmi fails to load due to conflict with amd-pmf bugzilla-daemon
2024-04-09 15:51 ` bugzilla-daemon
2024-04-09 15:57 ` bugzilla-daemon
2024-04-09 16:30 ` bugzilla-daemon
2024-04-10 1:15 ` bugzilla-daemon
2024-04-10 4:49 ` bugzilla-daemon
2024-04-10 5:03 ` bugzilla-daemon
2024-04-10 5:19 ` bugzilla-daemon
2024-04-10 5:29 ` bugzilla-daemon
2024-04-10 5:35 ` bugzilla-daemon
2024-04-10 5:35 ` bugzilla-daemon
2024-04-10 5:45 ` bugzilla-daemon
2024-04-10 6:05 ` bugzilla-daemon
2024-04-10 6:09 ` bugzilla-daemon
2024-04-10 6:10 ` bugzilla-daemon
2024-04-10 11:22 ` bugzilla-daemon
2024-04-10 11:24 ` bugzilla-daemon
2024-04-10 11:29 ` bugzilla-daemon
2024-04-10 11:30 ` bugzilla-daemon
2024-04-10 11:31 ` bugzilla-daemon
2024-04-10 11:35 ` bugzilla-daemon [this message]
2024-04-10 11:49 ` bugzilla-daemon
2024-04-10 11:52 ` bugzilla-daemon
2024-04-10 11:58 ` bugzilla-daemon
2024-04-10 12:28 ` bugzilla-daemon
2024-04-10 12:44 ` bugzilla-daemon
2024-04-10 14:24 ` bugzilla-daemon
2024-04-10 14:38 ` bugzilla-daemon
2024-04-10 14:45 ` bugzilla-daemon
2024-04-10 14:54 ` bugzilla-daemon
2024-04-10 15:22 ` bugzilla-daemon
2024-04-12 7:08 ` bugzilla-daemon
2024-04-12 11:21 ` bugzilla-daemon
2024-04-12 13:04 ` bugzilla-daemon
2024-04-12 13:32 ` bugzilla-daemon
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=bug-218685-215701-xzAe4xd3aT@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
/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.