- ENE CIR RECEIVER DRIVER SHOULD I REMOVE IT DRIVERS
- ENE CIR RECEIVER DRIVER SHOULD I REMOVE IT ARCHIVE
- ENE CIR RECEIVER DRIVER SHOULD I REMOVE IT PATCH
The above discussion John Garry is looking into this but I wanted to get HAS_IOPORT is set but these hardcoded I/O ports will not work.
ENE CIR RECEIVER DRIVER SHOULD I REMOVE IT DRIVERS
Numbers, this is not currently implemented but could still be added if weįind enough drivers that should not be compiled on platforms where HARDCODED_IOPORTS config option for drivers which use hardcoded I/O port One other thing thatĬame up during the discussion is the idea of adding a separate
ENE CIR RECEIVER DRIVER SHOULD I REMOVE IT PATCH
HAS_IOPORT, fixes a few trivial findings from the original patch discussionĪnd splits the patch into more manageable patches. This series builts heavily on an original patch for demonstating theĬoncept by Arnd Bergmann and was created in collaboration with him asĭiscussed in the follow up to his original patch rebases his patch on v5.16-rc7, adds the missing arch selects for Systems which do not need legacy PCI support to skip building drivers for While keeping I/O port accessors for non-legacy uses. Introduce another config option LEGACY_PCI to specifically disable theĬompilation of drivers for legacy PCI devices and legacy I/O space uses Not only used in legacy PCI devices or with legacy I/O spaces for backwardsĬompatible PCI Express devices, but also for example in ACPI we also Inb()/outb() and friends may not be defined. Invasive change, we believe that is indeed the right patch series aims to do exactly that by introducing a HAS_IOPORTĬonfig option akin to the existing HAS_IOMEM. That this really should be a compile-time check and, though a much more ThisĪpproach however was rejected by Linus in tha mail below with the argument Handling this case by generating a run-time warning on access. The way these stubs are implemented inĪsm-generic/io.h leads to compiler warnings because any use willĮssentially lead to a NULL pointer access. On such platforms I/O space accessors like inb()/outb() are merely Some platforms such as s390 do not support legacy PCI devices nor PCI I/O Vincent Chen, Paul Walmsley, Palmer Dabbelt, Albert Ou, Guo RenĬc: linux-kernel, linux-arch, linux-pci, linux-riscv, linux-csky To: Arnd Bergmann, Bjorn Helgaas, John Garry, Nick Hu, Greentime Hu, ` (32 more replies) 0 siblings, 33 replies 108+ messages in threadįrom: Niklas Schnelle 16:42 UTC ( / raw) 16:42 ` Kconfig: introduce and depend on LEGACY_PCI Niklas Schnelle
ENE CIR RECEIVER DRIVER SHOULD I REMOVE IT ARCHIVE
Kconfig: Introduce HAS_IOPORT and LEGACY_PCI options archive mirror help / color / mirror / Atom feed * Kconfig: Introduce HAS_IOPORT and LEGACY_PCI options 16:42 Niklas Schnelle
0 kommentar(er)
