On 21.10.20 21:19, Tim Wawrzynczak via coreboot wrote: > Currently there are 3 different "strapping" entries in the coreboot tables, > and with the recent addition of fw_config ( > https://review.coreboot.org/c/coreboot/+/41209), we would also like to add > the 64-bit fw_config field (updated here > https://review.coreboot.org/c/coreboot/+/45939) to the coreboot table as > well. > > In this patch (https://review.coreboot.org/c/coreboot/+/46605), I am > proposing to deprecate the 3 current "strapping" entries (board ID, ram > code and SKU ID), and add them all to 1 entry, containing board ID, ram > code, SKU ID as well as fw_config. This saves the overhead of parsing 4 > different entries to obtain board configuration information. > > Would like to hear any thoughts on this,
I'm actually very confused about these things and how they are supposed to be used. Is it correct to say that there are / would be coreboot table entries with board-specific encodings? Wouldn't it be better to decode the infos first and put that into tables so generic drivers can consume them? Generally, I wouldn't assume / want board-specific drivers outside of coreboot. It seems board-specific table entries would invite people to write such. Sorry if I completely misunderstood the intention of these entries. Nico _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
