From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg Kroah-Hartman Date: Tue, 28 Dec 2021 13:01:38 +0100 Subject: [Intel-wired-lan] [RFC 01/32] Kconfig: introduce and depend on LEGACY_PCI In-Reply-To: References: <20211227164317.4146918-1-schnelle@linux.ibm.com> <20211227164317.4146918-2-schnelle@linux.ibm.com> <20211228101435.3a55b983@coco.lan> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: intel-wired-lan@osuosl.org List-ID: On Tue, Dec 28, 2021 at 11:58:55AM +0100, Niklas Schnelle wrote: > We add both LEGACY_PCI and HAS_IOPORT to differentiate between two > cases. HAS_IOPORT is for PC-style devices that are not on a PCI card > while LEGACY_PCI is for PCI drivers that require port I/O. This > includes pre-PCIe devices as well as PCIe devices which require > features like I/O spaces. The "legacy" naming is comes from the PCIe > spec which in section 2.1.1.2 says "PCI Express supports I/O Space for > compatibility with legacy devices which require their use. Future > revisions of this specification may deprecate the use of I/O Space." Ah, then mention the reason why this is called LEGACY_PCI is that it is because that is what the PCI spec calls it. It was not obvious here at all that this is where the name came from. thanks, greg k-h