drivers/eisa/Kconfig
Source file repositories/reference/linux-study-clean/drivers/eisa/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/eisa/Kconfig- Extension
[no extension]- Size
- 2095 bytes
- Lines
- 76
- Domain
- Driver Families
- Bucket
- drivers/eisa
- Inferred role
- Driver Families: build/configuration rule
- Status
- atlas-only
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: GPL-2.0-only
#
# EISA configuration
#
config HAVE_EISA
bool
menuconfig EISA
bool "EISA support"
depends on HAVE_EISA
help
The Extended Industry Standard Architecture (EISA) bus was
developed as an open alternative to the IBM MicroChannel bus.
The EISA bus provided some of the features of the IBM MicroChannel
bus while maintaining backward compatibility with cards made for
the older ISA bus. The EISA bus saw limited use between 1988 and
1995 when it was made obsolete by the PCI bus.
Say Y here if you are building a kernel for an EISA-based machine.
Otherwise, say N.
config EISA_VLB_PRIMING
bool "Vesa Local Bus priming"
depends on X86 && EISA
default n
help
Activate this option if your system contains a Vesa Local
Bus (VLB) card that identify itself as an EISA card (such as
the Adaptec AHA-284x).
When in doubt, say N.
config EISA_PCI_EISA
bool "Generic PCI/EISA bridge"
depends on !PARISC && PCI && EISA
default y
help
Activate this option if your system contains a PCI to EISA
bridge. If your system have both PCI and EISA slots, you
certainly need this option.
When in doubt, say Y.
# Using EISA_VIRTUAL_ROOT on something other than an X86 may lead
# to crashes...
config EISA_VIRTUAL_ROOT
bool "EISA virtual root device"
depends on EISA && X86
default y
help
Activate this option if your system only have EISA bus
(no PCI slots).
When in doubt, say Y.
config EISA_NAMES
bool "EISA device name database"
depends on EISA
default y
help
By default, the kernel contains a database of all known EISA
device names to make the information in sysfs comprehensible
to the user. This database increases size of the kernel
image by about 40KB, but it gets freed after the system
boots up, so it doesn't take up kernel memory. Anyway, if
you are building an installation floppy or kernel for an
Annotation
- Atlas domain: Driver Families / drivers/eisa.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.