drivers/net/ethernet/sfc/falcon/Kconfig

Source file repositories/reference/linux-study-clean/drivers/net/ethernet/sfc/falcon/Kconfig

File Facts

System: Linux kernel
Corpus path: drivers/net/ethernet/sfc/falcon/Kconfig
Extension: [no extension]
Size: 660 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
config SFC_FALCON
	tristate "Solarflare SFC4000 support"
	depends on PCI
	select MDIO
	select CRC32
	select I2C
	select I2C_ALGOBIT
	help
	  This driver supports 10-gigabit Ethernet cards based on
	  the Solarflare SFC4000 controller.

	  To compile this driver as a module, choose M here.  The module
	  will be called sfc-falcon.
config SFC_FALCON_MTD
	bool "Solarflare SFC4000 MTD support"
	depends on SFC_FALCON && MTD && !(SFC_FALCON=y && MTD=m)
	default y
	help
	  This exposes the on-board flash and/or EEPROM as MTD devices
	  (e.g. /dev/mtd1).  This is required to update the boot
	  configuration under Linux.

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.