From: David Lazar <dlazar@gmail.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Hans de Goede <hdegoede@redhat.com>,
kys@microsoft.com, hpa@linux.intel.com, x86@kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
"Rafael J. Wysocki" <rafael@kernel.org>
Subject: Re: PIC probing code from e179f6914152 failing
Date: Wed, 25 Oct 2023 17:25:20 +0200 [thread overview]
Message-ID: <ZTkzYA3w2p3L4SVA@localhost> (raw)
In-Reply-To: <32bcaa8a-0413-4aa4-97a0-189830da8654@amd.com>
--- On Wed, 25 Oct 2023, Mario Limonciello wrote:
> David - can you see if the below helps your hardware?
The keyboard and mouse work fine with Thomas' patch.
I've uploaded the debug info to the bug:
https://bugzilla.kernel.org/attachment.cgi?id=305291&action=edit
next prev parent reply other threads:[~2023-10-25 15:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:50 PIC probing code from e179f6914152 failing Mario Limonciello
2023-10-18 22:50 ` Thomas Gleixner
2023-10-19 16:39 ` David Lazăr
2023-10-19 21:20 ` Mario Limonciello
2023-10-20 3:43 ` Mario Limonciello
2023-10-20 15:16 ` Hans de Goede
2023-10-20 17:13 ` Mario Limonciello
2023-10-23 15:59 ` Thomas Gleixner
2023-10-23 16:17 ` Mario Limonciello
2023-10-23 17:50 ` Thomas Gleixner
2023-10-23 17:59 ` Mario Limonciello
2023-10-25 9:23 ` Thomas Gleixner
2023-10-25 14:41 ` Mario Limonciello
2023-10-25 15:25 ` Mario Limonciello
2023-10-25 15:25 ` David Lazar [this message]
2023-10-25 17:31 ` Thomas Gleixner
2023-10-25 17:37 ` Rafael J. Wysocki
2023-10-25 21:04 ` [PATCH] x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility, Thomas Gleixner
2023-10-25 22:11 ` Mario Limonciello
2023-10-26 9:27 ` Re: Thomas Gleixner
2023-10-26 8:17 ` [PATCH] x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility Hans de Goede
2023-10-26 9:39 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
2023-10-27 18:46 ` tip-bot2 for Thomas Gleixner
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=ZTkzYA3w2p3L4SVA@localhost \
--to=dlazar@gmail.com \
--cc=bp@alien8.de \
--cc=hdegoede@redhat.com \
--cc=hpa@linux.intel.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).