On Sun, Dec 14, 2008 at 12:04 AM, Pattrick Hueper phueper@hueper.net wrote:
On Sat, Dec 13, 2008 at 11:37 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
There's one thing we have to decide on, though. Should all of this be committed as one big block or is a split into multiple patches preferable? I'd like at least one commit which mirrors the YABEL part of the SLOF tree (commit 0aab2795a986e76286386ebd02e59ca75a528538). Later changes can be grouped, but it never huts to have a reference point available, especially if there is a chance that the YABEL codebase may get some fixes in SLOF.
I agree, i would like to have:
- the original SLOF tree 0aab2795a986e76286386ebd02e59ca75a528538
- the original SLOF x86emu patches 9644fedf2dbbb2b3bcd4331758bc2e6a335ee8af
- and the rest grouped together
as separate commits. As you said, it makes sense to have a reference back to the SLOF source code.
I will prepare those patches (should be pretty easy with git) and resend them to the list.
Cheers, Patty
Ok, here are the updated patches.
- one for x86emu changes from SLOF 1.7.0-4 - one for unmodified biosemu from SLOF 1.7.0-4 - one for warning fixes in x86emu ( i think it makes sense to have these separate, they are not part of SLOF and only affect x86emu) - one for the integration of biosemu aka YABEL into coreboot
Patty