drivers/net/ethernet/meta/Kconfig
Source file repositories/reference/linux-study-clean/drivers/net/ethernet/meta/Kconfig
File Facts
- System
- Linux kernel
- Corpus path
drivers/net/ethernet/meta/Kconfig- Extension
[no extension]- Size
- 1069 bytes
- Lines
- 39
- 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.
- Touches IRQ or DMA behavior; this matters for the representative real-device path.
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
#
# Meta Platforms network device configuration
#
config NET_VENDOR_META
bool "Meta Platforms devices"
default y
help
If you have a network (Ethernet) card designed by Meta, say Y.
That's Meta as in the parent company of Facebook.
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 Meta cards. If you say Y, you will be asked for
your specific card in the following questions.
if NET_VENDOR_META
config FBNIC
tristate "Meta Platforms Host Network Interface"
depends on 64BIT || COMPILE_TEST
depends on !S390
depends on MAX_SKB_FRAGS < 22
depends on PCI_MSI
depends on PTP_1588_CLOCK_OPTIONAL
select NET_DEVLINK
select PAGE_POOL
select PCS_XPCS
select PHYLINK
select PLDMFW
help
This driver supports Meta Platforms Host Network Interface.
To compile this driver as a module, choose M here. The module
will be called fbnic. MSI-X interrupt support is required.
endif # NET_VENDOR_META
Annotation
- Atlas domain: Driver Families / drivers/net.
- Implementation status: atlas-only.
- IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.
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.