What is BDF in PCIe?
Quick note explaining BDF in PCIe for BIOS/UEFI and embedded firmware readers.
What is BDF in PCIe?
BDF (Bus/Device/Function) is the logical address used to identify a PCI/PCIe function.
Why it matters
- Explains how firmware discovers and configures PCI/PCIe devices.
- Helps debug missing devices, invalid BARs, and resource-allocation issues.
- Connects PCI configuration space with UEFI driver binding.
Practical example
Example: if Vendor ID reads as 0xFFFF, firmware may not be seeing the device on the bus, or the bus/device/function address may be wrong.
Quick checklist
- Does the device appear in PCI configuration space?
- Are Vendor ID, Device ID, Class Code, BARs, and bridge windows valid?
- Does the correct UEFI driver bind to the device handle?
Quick takeaway
BDF in PCIe is best debugged by connecting configuration-space data with UEFI handle/protocol state.
Related notes
- What is BAR in PCIe?
- What is PCI Configuration Space?
- What is PCI Root Bridge?
- What is Vendor ID and Device ID?
- What is PCI Resource Allocation?
Public references
Found this useful?
Save it or share it with someone learning firmware, BIOS/UEFI, and embedded systems.
Nội dung liên quan
Một số bài viết, ghi chú hoặc project có liên quan đến nội dung bạn vừa đọc.
What is PCI Configuration Space?
Quick note explaining PCI Configuration Space for BIOS/UEFI and embedded firmware readers.
What is BAR in PCIe?
Quick note explaining BAR in PCIe for BIOS/UEFI and embedded firmware readers.
What is Bridge Window in PCIe?
Quick note explaining Bridge Window in PCIe for BIOS/UEFI and embedded firmware readers.
Biến note thành bài viết hoàn chỉnh
Notes là nơi ghi nhanh khái niệm.