On Fri, May 31, 2013 at 08:32:16AM -0500, Dave Frodin wrote:
I see now, that's pretty slick. The problem I see with that approach is that coreboot would need to add all of these files for a family14 mainboard.
[...]
And all of these files for a family15 mainboard
[...]
Since at build time we only know what cpu family the rom is being built for and not (necessarily) what the exact graphics ID is.
The method I proposed would have one family specific "vendev-map.bin" file.
Yes, but it would be quite difficult to inspect vendev-map.bin. I think an ascii interface is preferable.
One could go a level up and make a "symbolic link" type in cbfs (this is effectively what my patch did). The advantage would be that cbfstool could display it in a nicer format.
-Kevin