STRUCT FW_PHY_NC(9)

💅 struct fw_phy_nc

okay so bestie, this is a page straight out of the Kernel API Manual and it's about struct fw_phy_nc — a little struct that lowkey runs the whole show for the RTL_FW_PHY_NC firmware. The layout is genuinely iconic because it's not just the struct, it's a whole sandwich:

<struct fw_phy_nc> + <info> + <firmware data>

so like the struct, then the info, then the firmware data. in that order. periodt. ✨

🦋 SYNOPSIS

struct fw_phy_nc {
    struct fw_block blk_hdr;
    __le16 fw_offset;
    __le16 fw_reg;
    __le16 ba_reg;
    __le16 ba_data;
    __le16 patch_en_addr;
    __le16 patch_en_value;
    __le16 mode_reg;
    __le16 mode_pre;
    __le16 mode_post;
    __le16 reserved;
    __le16 bp_start;
    __le16 bp_num;
    __le16 bp[4];
    char info[];
};

look at her. char info[] at the end with the flexible array moment — main character energy fr fr. 💅

🎀 Members

• blk_hdr — the firmware descriptor (it's got the type and the length, the lil ID card of the block).
• fw_offset — the offset of the firmware binary data. wanna know where the data actually starts? it's the address of struct fw_phy_nc + fw_offset. math girlie behaviour.
• fw_reg — the register you use to load the firmware. depends on chip, so don't come for me if it's not what you expected. 🫶
• ba_reg — the register where you write the base address. also depends on chip.
• ba_data — the base address itself. yep, chip-dependent again.
• patch_en_addr — the register for enabling patch mode. chip-dependent, obviously. 🌸
• patch_en_value — the patch mode enabled mask. this one depends on the firmware, not the chip — iykyk.
• mode_reg — the register for switching the mode.
• mode_pre — the mode that needs to be set before loading the firmware. pre-game ritual, literally.
• mode_post — the mode you set when you're done loading the firmware. cool-down era.
• reserved — reserved space. unused. she's just vibing there, taking up room, we respect her. 🙈
• bp_start — the start register of the break points. chip-dependent.
• bp_num — the number of break points that need to be set for this firmware. firmware-dependent.
• bp — the break points. depends on the firmware, bestie.
• info — extra info for debugging, and it's followed by the binary data of the firmware. so she's not the end of the struct, she's the doorway to the data. 💀

👑 SEE ALSO

go look at the kernel file ./drivers/net/usb/r8152.c — that's where the lore lives. also check out these iconic siblings:

• struct fw_block(9)
• struct fw_header(9)
• struct fw_mac(9)
• struct fw_phy_patch_key(9)

and that's the whole page, bestie 💖 this came from ./drivers/net/usb, dated October 2026, and it's filed under struct fw_phy_nc(9) — slay, go read the source, ily, bye 🎀✨