[coreboot] v3 patch rm elfboot
c-d.hailfinger.devel.2006 at gmx.net
Sat Feb 16 01:23:46 CET 2008
On 16.02.2008 00:19, Myles Watson wrote:
>> -----Original Message-----
>> From: ron minnich [mailto:rminnich at gmail.com]
>> Sent: Friday, February 15, 2008 4:12 PM
>> To: Myles Watson
>> Cc: Coreboot; Stefan Reinauer
>> Subject: Re: [coreboot] v3 patch rm elfboot
>> On Feb 15, 2008 2:59 PM, Myles Watson <mylesgw at gmail.com> wrote:
>>> So the use case is that you have a lar file, but don't have the ELF that
>>> you started with originally, and you want to put it into a different lar file?
>> yes. Because you have a board, and a new (e.g.) boot block, which you
>> have been sent via email from a company that is supporting your
>> platform, and can not for whatever
>> reason recreate the payload. You may have even lost the source to it.
>> This happens.
>>> It might be easier to remove the other things in the lar instead, or do
>>> a lar copy from one lar to a new lar, which wouldn't lose the entry points.
> Given that, I'd be willing to implement "add from lar", so that you can move
> lar files from one archive into another. It would be something like lar -aL
> larfile:larpath:newlarpath. I think going back to ELF is problematic
> because it wouldn't be a true ELF anymore. Would that be enough, Stefan?
> Anyone else?
You are not seriously proposing that "add from lar" mode, right? Even
parsing a MANIFEST file would be better than that. Sorry.
The easiest thing would be to create a MANIFEST file during unpacking
which looks like the output of "lar -l". All the information you'll ever
need to repack in one nice human-readable file. You can then decide how
lar should parse the file when recreating the archive, but in case the
original lar does not exist anymore, you have to do something useful
with the extracted contents.
The best thing would be to extract the LAR into sort of a fake ELF file,
just conforming enough to be parsed by lar without problems.
More information about the coreboot