Patch Set 1:
Anyway, I'm fine with putting these files here so they stick to convention of placing FSP headers. Patrick?
I'd prefer files that come from the outside and shouldn't be changed as part of coreboot development (e.g. a refactor) to end up in vendorcode. Of course they can be changed if their outside copy changes.
This also ties in with some of our lint tests which exclude vendorcode because it's exempt from some coding style rules that apply to the rest of the tree. So it's not just a personal preference ;-)
tl;dr: Everything that's built specifically for coreboot and is maintained as part of coreboot should end up in the appropriate locations in our tree. Everything that only ships with coreboot because we need it to build, but really comes from somewhere else: vendorcode.
Agreed. Being able to build-test the new coreboot code is something nice to have :-)
Patch set 5:Code-Review +2
1 comment:
File src/vendorcode/intel/fsp/fsp2_0/skylake_sp/hob_iiouds.h:
Are these extra indents necessary?
To view, visit change 39108. To unsubscribe, or for help writing mail filters, visit settings.