Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Rosen Penev <rosenp@gmail.com>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/8] x86/pci: move Intel chipset quirks to arch/x86/pci/fixup.c
Date: Sun, 12 Jul 2026 12:18:28 +0200	[thread overview]
Message-ID: <alNp9GFvMDN7yDQ3@wunner.de> (raw)
In-Reply-To: <20260707221800.920270-3-rosenp@gmail.com>

On Tue, Jul 07, 2026 at 03:17:54PM -0700, Rosen Penev wrote:
> Move Intel-specific PCI quirk handlers from drivers/pci/quirks.c to
> arch/x86/pci/fixup.c, where they logically belong as x86 platform code.
> The affected categories are:
> 
> - I82371FB PIIX3 passive release (quirk_passive_release)
> - 82437/82439 Triton PCI/PCI transfer limit (quirk_triton)
> - 82441/82443 Natoma PCI/PCI transfer limit (quirk_natoma)
> - PIIX4 ACPI/SMB IO region decode (quirk_piix4_acpi)
> - ICH4/ICH5 LPC ACPI & GPIO decode (quirk_ich4_lpc_acpi)
> - ICH6 LPC ACPI/GPIO & generic IO decode (quirk_ich6_lpc, ich6_lpc_acpi_gpio,
>   ich6_lpc_generic_decode)

These are all 32-bit chipsets.  We don't need to compile them into
modern 64-bit kernels.  They should be #ifdef'ed to CONFIG_X86_32,
or better yet, moved to a separate fixup_32.c file to reduce clutter
and make it easier to deprecate and remove 32-bit support one day.

However, I vaguely remember that some Intel chipsets of that day were
paired with DEC Alpha.  Triton maybe?

E.g. The Retro Web has some grainy Alpha motherboard pictures
and there are Intel chips soldered to those boards:

https://theretroweb.com/motherboards?itemsPerPage=24&chipsetIds[]=1886

I wouldn't be surprised if Intel PCI bridges such as 82380FB were
used on non-x86 boards like these.

And I'm definitely not surprised that LLMs think these are x86 only.
You'd have to train them with old data sheets, manuals, magazines,
otherwise they're just as clueless as anyone who hasn't lived through
that era.

> - ICH7-10 LPC generic IO decode (quirk_ich7_lpc, ich7_lpc_generic_decode)

ICH7 was used with Core Duo from 2006, I believe that was the first
southbridge to be paired with a 64-bit CPU.

Thanks,

Lukas

  reply	other threads:[~2026-07-12 10:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-07 22:17 [PATCH 0/8] x86/pci: consolidate x86-specific PCI quirks into arch/x86/pci/fixup.c Rosen Penev
2026-07-07 22:17 ` [PATCH 1/8] x86/pci: gate arch fixups with CONFIG_PCI_QUIRKS Rosen Penev
2026-07-07 22:17 ` [PATCH 2/8] x86/pci: move Intel chipset quirks to arch/x86/pci/fixup.c Rosen Penev
2026-07-12 10:18   ` Lukas Wunner [this message]
2026-07-12 10:33     ` Lukas Wunner
2026-07-07 22:17 ` [PATCH 3/8] x86/pci: move VIA " Rosen Penev
2026-07-07 22:17 ` [PATCH 4/8] x86/pci: move SiS " Rosen Penev
2026-07-07 22:17 ` [PATCH 5/8] x86/pci: move ALi " Rosen Penev
2026-07-07 22:17 ` [PATCH 6/8] x86/pci: move AMD x86 " Rosen Penev
2026-07-07 22:17 ` [PATCH 7/8] x86/pci: move x86 ifdef-gated " Rosen Penev
2026-07-07 22:18 ` [PATCH 8/8] x86/pci: move remaining x86-specific quirks to fixup.c Rosen Penev
2026-07-10 20:46 ` [PATCH 0/8] x86/pci: consolidate x86-specific PCI quirks into arch/x86/pci/fixup.c Bjorn Helgaas
2026-07-10 20:51   ` Rosen Penev
2026-07-10 21:27     ` Bjorn Helgaas

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=alNp9GFvMDN7yDQ3@wunner.de \
    --to=lukas@wunner.de \
    --cc=bhelgaas@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rosenp@gmail.com \
    --cc=tglx@kernel.org \
    --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