Re: OMAP baseline test results for v3.8-rc4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 21, 2013 at 01:24:19PM -0500, Matt Porter wrote:
> On Mon, Jan 21, 2013 at 06:20:03PM +0000, Richard Cochran wrote:
> > On Mon, Jan 21, 2013 at 10:45:10AM -0600, Nishanth Menon wrote:
> > > for MMC filesystem - we need the edma series. for a ramdisk, I am able
> > > to boot up to shell with 3.8-rc4 tag
> > 
> > Yep, I also could boot 3.8-rc3 using ramfs, no problem.
> 
> Do you use appended dtb? The only different that jumped out at me first
> Paul's reported hang is he uses appended dtb and I boot my boards with a
> single uImage and multiple dtbs the traditional DT way.

No, not appended. I have a u-boot that supports dtb:

  U-Boot SPL 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20)
  U-Boot 2012.10-rc1-00148-g4668a08 (Sep 30 2012 - 09:35:20)

and using the omap2plus_defconfig, with a minicom script like the one
below, and it works just fine.

HTH,
Richard


verbose on
send setenv ipaddr 192.168.1.77
send setenv serverip 192.168.1.12
send setenv netmask 255.255.255.0
send setenv bootargs console=ttyO0,115200n8 mem=256M root=/dev/ram rw initrd=0x82000000,16MB ramdisk_size=16384 earlyprintk=serial
send tftp 81000000 uImage
expect {
	"U-Boot# "
}
send tftp 82000000 beaglebone-initrd.gz
expect {
	"U-Boot# "
}
send tftp 80000000 am335x-bone.dtb
expect {
	"U-Boot# "
}
send bootm 81000000 - 80000000
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux