emac_set_type1addr(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– emac_set_type1addr β€” the kernel API manual, bestie edition πŸ’–

okay so this page is emac_set_type1addr(9) β€” it lives in the Kernel API Manual, section 9, and it's giving "tiny function, big friend group" energy. Let's get into it πŸŽ€


✨ NAME ✨

emac_set_type1addr β€” Set EMAC Type1 mac address πŸ’…

like, it sets the Type1 MAC address. that's the whole gig. icon behavior honestly.


🌸 SYNOPSIS 🌸

void emac_set_type1addr (struct emac_priv *priv , u32 ch , char
*mac_addr );

no cap, that's the whole signature. it returns void, so don't go looking for a return value, she's not coming 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • priv β€” the DaVinci EMAC private adapter structure. like, the whole adapter's personal info. her little diary πŸ’œ
  • ch β€” RX channel number. which channel we're talking about, fr fr.
  • mac_addr β€” MAC address to set in device. the actual address getting planted in there ✨

πŸ‘‘ DESCRIPTION πŸ‘‘

So here's the tea: this gets called internally to set the Type1 mac address of the adapter (Device). it's not a "hey user, call me directly" situation β€” this is an internal function doing internal function things πŸ’…

And the return story? It "Returns success (0) or appropriate error code (none as of now)". so like, the docs say it returns 0 on success or an appropriate error code, but as of right now there's no error code. so... it's void in the synopsis but the description talks about returning 0. yes bestie, that's exactly as contradictory as the original says. i don't make the rules, i just report them 😭

ngl, if you're reading this hoping for a return value to check β€” the synopsis says void and the description says (none as of now), so... vibe check passed but the error code did not show up πŸ’€

🌈 SEE ALSO 🌈

the whole extended friend group, no one left out, periodt:


and that's the page!! πŸŽ€ cute little sign-off for you: this one's sourced from ./drivers/net/ethernet/ti and dated October 2026, manual emac_set_type1addr(9). slay, go read some more kernel docs bestie πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from