> -----Original Message----- > From: Carl-Daniel Hailfinger [mailto:[EMAIL PROTECTED] > Sent: Monday, February 18, 2008 10:38 AM > To: ron minnich > Cc: Myles Watson; Stefan Reinauer; Coreboot > Subject: Re: [coreboot] v3 patch rm elfboot > > On 18.02.2008 18:19, ron minnich wrote: > > I dropped this idea on Stefan and he tells me I am not insane. I even > > did it BEFORE coffee :-) > > > > Could a LAR contain more LAR files? i.e. could LAR be recursive. > > > > Please don't! See the end of the mail for my reasons.
I agree. I don't think it's needed. > > > The recursive nature of LAR files could be trivially mirrored in the > code. > > > > So, we could have this: > > normal/payload.lar > > > > then, the payload would BE a LAR, and to move it to another LAR, > > lar -x bios.bin normal/payload.lar > > lar -a newbios.bin payload.lar:normal/payload.lar > > I don't see the need for the intermediate step. Since lar reads lar files, why not make it so that lar can add entries from other lar files? > > Why not have an option/compression specifier like "nocompress:"? We > could call it "copy:" and it would copy the individual members of the > old LAR to the new LAR. No code changes in lib/lar.c needed. > I think we can still use compression flags, and have the code decide whether it needs to re-compress the entries. Thanks, Myles -- coreboot mailing list [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
