From: Andi Kleen <ak@linux.intel.com>
To: Hans de Goede <hansg@kernel.org>
Cc: David Airlie <airlied@linux.ie>, Lukas Wunner <lukas@wunner.de>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/3] agp/amd64: Remove support for probing unlisted PCI devices
Date: Mon, 7 Jul 2025 11:12:11 -0700 [thread overview]
Message-ID: <aGwN-0-wC25534q7@tassilo> (raw)
In-Reply-To: <20250707173710.313701-1-hansg@kernel.org>
On Mon, Jul 07, 2025 at 07:37:07PM +0200, Hans de Goede wrote:
> Hi all,
>
> As discussed in this thread:
>
> https://lore.kernel.org/dri-devel/b29e7fbfc6d146f947603d0ebaef44cbd2f0d754.1751468802.git.lukas@wunner.de/
>
> The amd64_agp driver's support for trying to probe unsupported devices does
> not make sense anymore given that no new AGP devices have been produced for
> a while now.
It's not about AGP devices. By the time the K8 existed it was already
PCI only.
The K8 CPU integrated northbridge uses PCI AGP enumeration to expose its
integrated IOMMU, but it's not real AGP, just uses a mechanism similar
to the AGP aperture.
But you still have to probe the chipset hostbridge, and for these CPUs there
were multiple third party chipsets with different PCI IDs, so it needed
an own ID for each of them.
The reason why it's not needed is that there are no new third party K8
chipsets anymore.
-Andi
prev parent reply other threads:[~2025-07-07 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 17:37 [PATCH 0/3] agp/amd64: Remove support for probing unlisted PCI devices Hans de Goede
2025-07-07 17:37 ` [PATCH 1/3] agp/amd64: Check AGP Capability before binding to unsupported devices Hans de Goede
2025-07-07 17:37 ` [PATCH 2/3] agp/amd64: Change agp_try_unsupported default to 0 Hans de Goede
2025-07-07 17:37 ` [PATCH 3/3] agp/amd64: Remove support for probing unlisted PCI devices Hans de Goede
2025-07-07 18:00 ` Lukas Wunner
2025-07-07 18:12 ` Andi Kleen [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=aGwN-0-wC25534q7@tassilo \
--to=ak@linux.intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansg@kernel.org \
--cc=lukas@wunner.de \
/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.