<dec f='src/src/sys/dev/pci/if_sk.c' l='185' type='u_int8_t sk_vpd_readbyte(struct sk_softc * , int )'/>
<def f='src/src/sys/dev/pci/if_sk.c' l='323' ll='340' type='u_int8_t sk_vpd_readbyte(struct sk_softc * sc, int addr)'/>
<use f='src/src/sys/dev/pci/if_sk.c' l='350' u='c' c='sk_vpd_read_res'/>
<use f='src/src/sys/dev/pci/if_sk.c' l='380' u='c' c='sk_vpd_read'/>
<use f='src/src/sys/dev/pci/if_sk.c' l='398' u='c' c='sk_vpd_read'/>
<doc f='src/src/sys/dev/pci/if_sk.c' l='312'>/*
 * The VPD EEPROM contains Vital Product Data, as suggested in
 * the PCI 2.1 specification. The VPD data is separared into areas
 * denoted by resource IDs. The SysKonnect VPD contains an ID string
 * resource (the name of the adapter), a read-only area resource
 * containing various key/data fields and a read/write area which
 * can be used to store asset management information or log messages.
 * We read the ID string and read-only into buffers attached to
 * the controller softc structure for later use. At the moment,
 * we only use the ID string during sk_attach().
 */</doc>
