Ok, neither Felix or Florian like not having the DEADC0DE generated in the generic case, but with Florian I've come up with a scheme that leave all the other boards alone and only deals with the ones that need fixing (certain brcm63xx ones). Please let me know what you think.
What I'm thinking is that for the weird routers the imagetag doesn't create the DEADC0DE marker; instead we have a firstboot flag. If there is a firstboot flag true we see if following the DEADC0DE marker we have an offset and CRC32 that is created by the offset. If there is, we assume there is a valid jffs2 because it was created by the -j paramter to mtd. If not we create the DEADC0DE jffs immediately following the squashfs. In either case we unset the firstboot flag, recalculate the CRC and reflash the imagetag erase block. Then we let jffs2 creation carry on as usual. It's complicated but it doesn't mess with the other boards We should also disallow a jffs2 only filesystem on those routers because I don't see anyway to make that work It doesn't mess with the partition, so as long as the router isn't rebooted in middle of the flashing, we're okay. -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore (Daniel Dickinson's Website) http://www.bmts.com/~cshore
signature.asc
Description: PGP signature
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
