drivers/net/ethernet/wangxun/txgbevf/txgbevf_type.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/wangxun/txgbevf/txgbevf_type.h

Extension

.h

Size

1041 bytes

Lines

27

Domain

Driver Families

Bucket

drivers/net

Inferred role

Driver Families: implementation source

Status

source implementation candidate

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

#ifndef _TXGBEVF_TYPE_H_
#define _TXGBEVF_TYPE_H_

/* Device IDs */
#define TXGBEVF_DEV_ID_SP1000                  0x1000
#define TXGBEVF_DEV_ID_WX1820                  0x2000
#define TXGBEVF_DEV_ID_AML500F                 0x500F
#define TXGBEVF_DEV_ID_AML510F                 0x510F
#define TXGBEVF_DEV_ID_AML5024                 0x5024
#define TXGBEVF_DEV_ID_AML5124                 0x5124
#define TXGBEVF_DEV_ID_AML503F                 0x503f
#define TXGBEVF_DEV_ID_AML513F                 0x513f

#define TXGBEVF_MAX_MSIX_VECTORS               2
#define TXGBEVF_MAX_RSS_NUM                    4
#define TXGBEVF_MAX_RX_QUEUES                  4
#define TXGBEVF_MAX_TX_QUEUES                  4
#define TXGBEVF_DEFAULT_TXD                    128
#define TXGBEVF_DEFAULT_RXD                    128
#define TXGBEVF_DEFAULT_TX_WORK                256
#define TXGBEVF_DEFAULT_RX_WORK                256

#endif /* _TXGBEVF_TYPE_H_ */

Annotation

• Atlas domain: Driver Families / drivers/net.
• Implementation status: source implementation candidate.
• 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.