On Sat, Apr 28, 2007 at 11:14:27AM +0200, Martin Michlmayr wrote: > Package: apex-nslu2 > Version: 1.4.15 > > At the moment, the versions of apex-nslu2 are not written to flash. > We need to figure out some way to do this eventually. I suppose we > could copy some code from flash-kernel to apex-nslu2's postinst, or > maybe have apex-nslu2 depend on flash-kernel and then have > apex-nslu2's postinst call flash-kernel in some special way.
Let me see if I understand what you are saying. When users upgrade apex, they don't get a new boot loader as they would expect with LILO or GRUB. Sounds like a reasonable thing to do for them as long as it is already installed. We can use the environment scanning application to determine if APEX is present. > The other problem is that Debian's flash is padded with zeros rather > than FFs as APEX expects. So we might have to store the environment, > clear it (with FFs) and then restore it. Some initial thoughts on > this can be found in > http://lists.debian.org/debian-arm/2007/02/msg00014.html > but I'm not sure I'm the right person to work on this. If we are going to automate the procedure of reflashing the boot loader, we can add support for clearing the environment when we do this. > Joey, do you think look into this? Is there an important reason why Debian pads with zeroes? Cheers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
