drivers/net/ethernet/brocade/Kconfig
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/brocade/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/brocade/Kconfig- Extension
[no extension]- Size
- 620 bytes
- Lines
- 23
- Domain
- Driver Families
- Bucket
- drivers/net
- 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
#
# QLogic BR-series device configuration
#
config NET_VENDOR_BROCADE
bool "QLogic BR-series devices"
default y
depends on PCI
help
If you have a network (Ethernet) card belonging to this class, say Y.
Note that the answer to this question doesn't directly affect the
kernel: saying N will just cause the configurator to skip all
the questions about QLogic BR-series cards. If you say Y, you will be
asked for your specific card in the following questions.
if NET_VENDOR_BROCADE
source "drivers/net/ethernet/brocade/bna/Kconfig"
endif # NET_VENDOR_BROCADE
Annotation
- Atlas domain: Driver Families / drivers/net.
- 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.