From: Hans de Goede <hdegoede@redhat.com>
To: Konrad J Hambrick <kjhambrick@gmail.com>
Cc: "Werner Sembach" <wse@tuxedocomputers.com>,
"Bjorn Helgaas" <helgaas@kernel.org>,
linux-pci@vger.kernel.org,
"Florent DELAHAYE" <kernelorg@undead.fr>,
"Matt Hansen" <2lprbe78@duck.com>,
"Benoit Grégoire" <benoitg@coeus.ca>,
"Nicholas Johnson" <nicholas.johnson-opensource@outlook.com.au>,
"Mika Westerberg" <mika.westerberg@linux.intel.com>,
mumblingdrunkard@protonmail.com, linux-kernel@vger.kernel.org,
"Bjorn Helgaas" <bhelgaas@google.com>
Subject: Re: [PATCH 0/4] PCI: Continue E820 vs host bridge window saga
Date: Mon, 5 Dec 2022 20:21:51 +0100 [thread overview]
Message-ID: <38bc80ac-0f19-eaa1-5076-b5487aa52ee4@redhat.com> (raw)
In-Reply-To: <CANBHt+MoHWz6nB39N3vCM8OkWcjqn_5Va-_bbEcknYDQ3Ve8=Q@mail.gmail.com>
Hi,
On 12/5/22 17:29, Konrad J Hambrick wrote:
>
>
> On Mon, Dec 5, 2022 at 8:26 AM Hans de Goede <hdegoede@redhat.com <mailto:hdegoede@redhat.com>> wrote:
>
>
> > Do you mean the X170KM-G? I don't think it has the option to switch to Legacy BIOS mode (At least i didn't found an option in the bios version i have)
>
> I'm talking about this patch:
>
> https://lore.kernel.org/linux-pci/20221010150206.142615-1-hdegoede@redhat.com/ <https://lore.kernel.org/linux-pci/20221010150206.142615-1-hdegoede@redhat.com/>
>
> Regards,
>
> Hans
>
>
> Hans --
>
> I applied Bjorn's four Patches last night and built 6.1-rc8 and the 'Clevo X170KM-G Barebone' Quirk is still in the pci_crs_quirks[] array in arch/x86/pci/acpi.c, even after I applied Bjorn's Patches.
Right that is expected, the point which I was trying to make is, that at least for
those models which support Legacy BIOS mode, we need to keep the quirks around.
> I am stuck on a project for my 'real job' and I won't be free until this evening.
>
> Do you still need a set of logs from 6.1-rc8 ?
I don't remember ever asking for logs in this email thread. I guess Bjorn maybe
asked for logs? Assuming I have that right I will leave answering the question
if logs are still necessary up to Bjorn.
Regards,
Hans
prev parent reply other threads:[~2022-12-05 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 21:18 [PATCH 0/4] PCI: Continue E820 vs host bridge window saga Bjorn Helgaas
2022-12-02 21:18 ` [PATCH 1/4] efi/x86: Remove EfiMemoryMappedIO from E820 map Bjorn Helgaas
2022-12-02 21:18 ` [PATCH 2/4] PCI: Skip allocate_resource() if too little space available Bjorn Helgaas
2022-12-02 21:18 ` [PATCH 3/4] x86/PCI: Tidy E820 removal messages Bjorn Helgaas
2022-12-02 21:18 ` [PATCH 4/4] x86/PCI: Fix log message typo Bjorn Helgaas
2022-12-03 12:44 ` [PATCH 0/4] PCI: Continue E820 vs host bridge window saga Hans de Goede
2022-12-03 17:57 ` Bjorn Helgaas
2022-12-04 9:13 ` Hans de Goede
2022-12-07 15:31 ` Hans de Goede
2022-12-08 18:57 ` Bjorn Helgaas
2022-12-08 19:16 ` Hans de Goede
2022-12-08 20:06 ` Bjorn Helgaas
2022-12-08 20:19 ` Hans de Goede
2022-12-04 9:29 ` Hans de Goede
2022-12-05 13:27 ` Werner Sembach
2022-12-05 14:26 ` Hans de Goede
[not found] ` <CANBHt+MoHWz6nB39N3vCM8OkWcjqn_5Va-_bbEcknYDQ3Ve8=Q@mail.gmail.com>
2022-12-05 19:21 ` 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=38bc80ac-0f19-eaa1-5076-b5487aa52ee4@redhat.com \
--to=hdegoede@redhat.com \
--cc=2lprbe78@duck.com \
--cc=benoitg@coeus.ca \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kernelorg@undead.fr \
--cc=kjhambrick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=mumblingdrunkard@protonmail.com \
--cc=nicholas.johnson-opensource@outlook.com.au \
--cc=wse@tuxedocomputers.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