Hauke Mehrtens <ha...@hauke-m.de> writes: > Ferenc Wagner wrote: > >> How well is Linux 2.6.30 on brcm47xx supposed to work? The flash >> driver seems to have some problem at least: >> >> flash init: 0x1c000000 0x02000000 >> Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank >> Intel/Sharp Extended Query Table at 0x0035 >> Using auto-unlock on power-up/resume >> cfi_cmdset_0001: Erase suspend on write enabled >> Flash device: 0x200000 at 0x1fc00000 >> bootloader size: 262144 >> Creating 4 MTD partitions on "Physically mapped flash": >> 0x000000000000-0x000000040000 : "cfe" >> 0x000000040000-0x0000001f0000 : "linux" >> 0x000000116000-0x0000001f0000 : "rootfs" >> mtd: partition "rootfs" doesn't start on an erase block boundary -- force >> read-only >> mtd: partition "rootfs_data" created automatically, ofs=65C0000, >> len=FFFFFFFFF9C30000 >> 0x0000065c0000-0x0000001f0000 : "rootfs_data" >> mtd: partition "rootfs_data" is out of reach -- disabled >> 0x0000001f0000-0x000000200000 : "nvram" >> >> Splitting rootfs arrives at a wrong offset/length pair. >> (Otherwise the kernel boots into userspace just fine.) > > I looks like your flash chip is only 2MB big, that is too small for an > image with kernel 2.6.
Yes, for a prebuilt image, but not for a manually trimmed-down one. > Did it boot with kernel 2.6.28? If yes, please post the the same output > with that kernel. Sure, here it is (with a higher log level, from dmesg): flash init: 0x1c000000 0x02000000 Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0035 Using auto-unlock on power-up/resume cfi_cmdset_0001: Erase suspend on write enabled Flash device: 0x200000 at 0x1fc00000 bootloader size: 262144 Updating TRX offsets and length: old trx = [0x0000001c, 0x0000090c, 0x000a8800], len=0x00181000 crc32=0xcde8e3d0 new trx = [0x0000001c, 0x0000090c, 0x000a8800], len=0x000a8800 crc32=0xd5a3c0a2 Done Creating 4 MTD partitions on "Physically mapped flash": 0x00000000-0x00040000 : "cfe" 0x00040000-0x001f0000 : "linux" 0x000e8800-0x001f0000 : "rootfs" mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only mtd: partition "rootfs" set to be root filesystem mtd: partition "rootfs_data" created automatically, ofs=1B0000, len=40000 0x001b0000-0x001f0000 : "rootfs_data" 0x001f0000-0x00200000 : "nvram" Or with a bigger 2.6.28 kernel: Creating 4 MTD partitions on "Physically mapped flash": 0x00000000-0x00040000 : "cfe" 0x00040000-0x001f0000 : "linux" 0x00110800-0x001f0000 : "rootfs" mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only mtd: partition "rootfs_data" created automatically, ofs=1D0000, len=20000 0x001d0000-0x001f0000 : "rootfs_data" 0x001f0000-0x00200000 : "nvram" But also 2.6.30 booted into user space, as I wrote above. -- Thanks, Feri. _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
