drivers/net/ethernet/emulex/benet/Kconfig
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/emulex/benet/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/emulex/benet/Kconfig- Extension
[no extension]- Size
- 1368 bytes
- Lines
- 53
- 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
config BE2NET
tristate "ServerEngines' 10Gbps NIC - BladeEngine"
depends on PCI
help
This driver implements the NIC functionality for ServerEngines'
10Gbps network adapter - BladeEngine.
config BE2NET_HWMON
bool "HWMON support for be2net driver"
depends on BE2NET && HWMON
depends on !(BE2NET=y && HWMON=m)
default y
help
Say Y here if you want to expose thermal sensor data on
be2net network adapter.
config BE2NET_BE2
bool "Support for BE2 chipsets"
depends on BE2NET
default y
help
Say Y here if you want to use devices based on BE2
chipsets. (e.g. OneConnect OCe10xxx)
config BE2NET_BE3
bool "Support for BE3 chipsets"
depends on BE2NET
default y
help
Say Y here if you want to use devices based on BE3
chipsets. (e.g. OneConnect OCe11xxx)
config BE2NET_LANCER
bool "Support for Lancer chipsets"
depends on BE2NET
default y
help
Say Y here if you want to use devices based on Lancer
chipsets. (e.g LightPulse LPe12xxx)
config BE2NET_SKYHAWK
bool "Support for Skyhawk chipsets"
depends on BE2NET
default y
help
Say Y here if you want to use devices based on Skyhawk
chipsets. (e.g. OneConnect OCe14xxx)
comment "WARNING: be2net is useless without any enabled chip"
depends on BE2NET_BE2=n && BE2NET_BE3=n && BE2NET_LANCER=n && \
BE2NET_SKYHAWK=n && BE2NET
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.