check_eeprom(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– check_eeprom(9) πŸ’–

okay so this one lives in the Kernel API Manual and honestly bestie, it's a little shy β€” two arguments, one job, and a whole lot of friends in SEE ALSO. let's get into it 🫢


✨ NAME ✨

check_eeprom β€” literally just get the contents of the eeprom and check 'em πŸ’…


🌸 SYNOPSIS 🌸

void check_eeprom (struct NvRamType *eeprom , unsigned long io_port );

no cap, that's the whole signature πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • eeprom β€” a strcuture that you, the caller, allocated, and that the eeprom data gets read into. yes, it's your memory, your responsibility, main character energy πŸ‘‘
  • io_port β€” the io port to read from. that's the one, that's the port πŸŒ€

πŸ’… DESCRIPTION πŸ’…

So what happens is: it reads seeprom for 128 bytes and drops them into the memory provider in eeprom. 🌈

Then β€” and this is the important part β€” it checks the checksum. and if the checksum is not correct?? 😭 it does not panic, it does not cry, it just uses a set of default values instead. iconic behaviour honestly. resilient queen. πŸ‘‘

lowkey a vibe check for your eeprom: if the checksum doesn't pass, defaults it is πŸ“

πŸ”₯ SEE ALSO πŸ”₯

the group chat is huge, bestie. all of these hang out in the kernel file ./drivers/scsi/dc395x.c:

like I said. the whole friend group. iykyk πŸ’œ


and that's the page!! this one came from ./drivers/scsi, dated October 2026 β€” check_eeprom(9) out, mwah πŸ’‹βœ¨πŸŽ€

πŸ“¦ where this page comes from