On Sat, 2011-07-23 at 18:57 +0200, Bdale Garbee wrote: > On Sat, 23 Jul 2011 17:57:03 +0200, Ben Hutchings <ben@decadent.org.uk> wrote: > Non-text part: multipart/signed > > Why would the user have to do that? Your hook script can do it. > > I'm completely lost. How can a hook script update u-boot's path > definitions? By writing to whichever flash partition they're in. > Unlike with EFI firmware where we have efibootmgr, I'm not aware of a > tool that runs in Linux userspace that has the ability to manipulate > u-boot's idea of the paths to the desired default kernel and initrd > images. Is that because, as with everything on ARM, it's done differently on each board? How do users set these variables in the first place? Ben. -- Ben Hutchings Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
Attachment:
signature.asc
Description: This is a digitally signed message part