Marc Singer wrote: > On Mon, Aug 14, 2006 at 09:31:48AM +0930, Rod Whitby wrote: >> It was my request that the FIS partition which starts at the Linksys >> RamDisk location contains a valid SerComm header (just like the first >> kernel partition). As for subsequent partitions, I see no reason to put >> a SerComm header on them. > > That's what I thought. Perhaps you can convince Martin. ;-)
I thought that's what we'd all agreed on :-( >> So an APEX-managed flash image has the same number of SerComm headers in >> the same locations as a standard Linksys flash image. That's all I'm >> asking for. I'd prefer that there were no other SerComm headers added >> to any other partitions. > > I, too, would prefer that. In fact, if we were to do that, we could > should the kernel partition to skip the initial sercomm header as well > as the one in the middle (which we are already skipping). This would > then present the same view of the kernel we do for the initrd. > > > apex> copy fis://kernel $bootaddr > apex> copy fis://ramdisk $ramdiskaddr > > Now that's clear. Indeed. -- Rod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
