Hi Wu, Le Thursday 17 June 2010 15:31:19, Wu Zhangjin a écrit : > Hi, > > On Thu, 2010-06-17 at 14:38 +0200, Florian Fainelli wrote: > > Hi, > > > > On Thursday 17 June 2010 14:20:49 wu zhangjin wrote: > > > Hi, > > > > > > I just got a bcm1250a board, it also uses the CFE as the bootloader, I > > > compiled a compressed vmlinuz-2.6.34 for it and boot with the > > > following command, it works well: > > > > > > CFE> setenv bootargs root=/dev/nfs rw > > > nfsroot=$nfs_server_ip:/path/to/nfs_root_fs ip=dhcp > > > CFE> ifconfig -auto eth0 > > > CFE> boot -elf $tftp_server_ip:/path/to/vmlinuz > > > > > > With -elf, the boot command of CFE can parse the vmlinuz and boot it > > > normally. I think you have used the wrong options of the boot command. > > > > CFE on bcm12xx, on bcm47xx and bcm63xx are all three slightly different > > flavors which may not behave exactly the same way wrt the load command. > > > > Also, you are on a development board so there are no reasons to restrict > > CFE commands, this is not the case with end-user products like WRT54G > > and such. > > Hmm, Maybe, I have no such products to test, anybody have such products, > welcome to test it ;) I just ran into the issue described by Waldemar on a BCM6348 board. You mentionned you were writing a patch, do you have one I could test on BCM63xx? -- Florian
