drivers/net/ethernet/alacritech/Kconfig
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/alacritech/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/alacritech/Kconfig- Extension
[no extension]- Size
- 932 bytes
- Lines
- 30
- 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 NET_VENDOR_ALACRITECH
bool "Alacritech devices"
default y
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 Alacritech devices. If you say Y, you will be asked
for your specific device in the following questions.
if NET_VENDOR_ALACRITECH
config SLICOSS
tristate "Alacritech Slicoss support"
depends on PCI
select CRC32
help
This driver supports Gigabit Ethernet adapters based on the
Session Layer Interface (SLIC) technology by Alacritech.
Supported are Mojave (1 port) and Oasis (1, 2 and 4 port) cards,
both copper and fiber.
To compile this driver as a module, choose M here: the module
will be called slicoss. This is recommended.
endif # NET_VENDOR_ALACRITECH
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.