[coreboot] Need new type for CBFS

Thomas Jourdan tjourdan at neuf.fr
Mon Aug 10 00:02:46 CEST 2009

Hi guys

Thanks for those clarifications. When I read the cbfs documentation, I
understood that for custom types, NULL was the correct type to use. The
documentation isn't really clear on this :

"There is a 4th component type ,defined as NULL (0xFFFFFFFF). This is
the "don't care" component type. This can be used when the component
type is not necessary (such as when the name of the component is unique.
i.e. option_table). It is recommended that all components be assigned a
unique type, but NULL can be used when the type does not matter."

I thought that the type parameter you enter when adding a component in
the cbfs file shall be one of the predefined string. I didn't know that
it could be any integer number (except the predefined ones).

Indeed, it works a lot better when I use a custom type.


Le dimanche 09 août 2009 à 11:16 -0700, ron minnich a écrit :
> Definitely don't use NULL for anything -- it's a free space marker as
> patrick points out.
> The type is actually
>         unsigned int type;
> I would make the following proposal: we reserve the range 0-255 for
> cbfs "system" (i.e. coreboot) use and open up the rest of the range
> for any other use. Then we allow people to register types on the wiki
> in some way.
> I can't believe coreboot will ever need more than 256 types, and I
> can't believe the community will ever need more than 16M.
> ron

More information about the coreboot mailing list