John,
Just tried out your new patch. It complains missing zlib.h file. I
search my linux src tree, and of course it is not there (otherwise it
won't complain). Since I have cross-compiled zlib-1.1.3 on my machine
so I change the jffs.c to use the zlib.h file in that zlib-1.1.3
package. Now my compilation stopped at linking stage with the following
error:
...
...
gcc -o zbsdchksum zbsdchksum.c
arm-linux-ld -v -Ttext=0x0 -Tdata=0x15300 -Bstatic -o bootldr-elf
boot-sa1100.o mmu-strongarm.o bootldr.o btflash.o heap.o xmodem.o
bsdsum.o modem.o getcmd.o jffs.o
-L/usr/local/arm-linux/lib/gcc-lib/arm-linux/2.95.2 -L. -lgcc -lc -lz
arm-linux-ld: section .rodata [00011ae8 -> 0001540d] overlaps section
.data [00015300 -> 00017197]
GNU ld version 2.10 (with BFD 2.10)
make: *** [bootldr] Error 1
I use pre-built arm-linux toolchain available on the net.
Regards,
Leonard Ye
John G Dorsey wrote:
> Leonard Ye wrote:
>
>
>> 4) bootldr + MTD + JFFS. This is the best combination. No DRAM is
>> wasted and the filesystem can be updated on-the-fly.
>
>
> As it turns out, the JFFS v1 code in the snapshot I released a few days
> ago wasn't amazingly broken. I've placed a new snapshot online which,
> barring more glaring oversights by me, should work on Assabet. (I've
> done some quick sanity checks booting from JFFS on a phase 4
> Assabet/Neponset and a phase 5 Assabet. No promises, though. =)
>
> ftp://ftp.wearablegroup.org/pub/software/patches/
> bootldr-snapshot-11-mar-2001.patch.gz
>
> Note that when you `load jffs' now, the entire "jffs" partition is
> erased (no need for `eraseall' or similar). The partition map that
> bootldr assumes for Assabet (phases 4 and 5) is included in the preamble
> to the patch; the correct root device for this map is "/dev/mtdblock2".
>
> I wouldn't try the JFFS2 support just yet.
>
> -jd
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
