On 10/21/2014 08:04 PM, Simon Glass wrote:
Hi Stephen,
On 20 October 2014 20:23, Stephen Warren swarren@wwwdotorg.org wrote:
On 10/19/2014 09:14 PM, Simon Glass wrote:
Hi Stephen,
On 17 October 2014 20:51, Stephen Warren swarren@wwwdotorg.org wrote:
On 09/30/2014 07:41 PM, Stephen Warren wrote:
On 09/22/2014 05:30 PM, Simon Glass wrote:
This series adds driver model support to the GPIO and serial drivers used by Raspberry Pi, and moves Raspberry Pi over to driver model.
This requires adding driver model support to the pl01x serial driver, and replacing the bcm2835 GPIO driver with a driver model version (since there are no longer clients that don't use driver model).
See u-boot-dm.git branch rpi-working for the tree this is based on.
The series, Tested-by: Stephen Warren swarren@wwwdotorg.org
Hmm. I take that back. Patch 4 causes a problem, at least when applied on top of u-boot/master from today.
Basic serial output works just fine, and I can interact with U-Boot without issue. However, when the boot scripts execute and load an extlinux.conf, U-Boot hangs. Up to patch 3, everything is fine.
U-Boot 2014.10-00004-g7830ed7 (Oct 17 2014 - 20:47:19)
DRAM: 480 MiB WARNING: Caches not enabled MMC: bcm2835_sdhci: 0 Using default environment
In: serial Out: lcd Err: lcd reading /uEnv.txt 24 bytes read in 14 ms (1000 Bytes/s) Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf reading /extlinux/extlinux.conf (U-Boot hangs here)
Can you please point me to where I can get an image to try this with? Also did you check with dm/next? There may be dependent patches, although the nature of the problem suggests not.
I use (a pretty old version of, but I doubt that matters) RPi Foundation's Raspbian image, and compiled the kernel and U-Boot according to:
http://elinux.org/index.php?title=RPi_Upstream_Kernel_Compilation&oldid=...
I installed the Raspbian image but I don't get uImg.txt nor the same boot sequence. I am able to boot a kernel though.
The RPi Foundation images boot their kernel directly from their binary firmware, and hence don't include any U-Boot or U-Boot boot scripts.
I haven't used boot.scr for a while, but this is apparently what's in mine:
load ${devtype} ${devnum}:1 ${kernel_addr_r} /zImage load ${devtype} ${devnum}:1 ${fdt_addr_r} /${fdtfile} setenv bootargs "earlyprintk loglevel=8 console=ttyAMA0 console=tty1 \ verbose rootwait root=/dev/mmcblk0p2 rw" bootz ${kernel_addr_r} - ${fdt_addr_r}
I use extlinux/extlinux.conf now, with the following content:
TIMEOUT 100 DEFAULT default MENU TITLE Boot menu
LABEL default MENU LABEL Default kernel LINUX ../zImage FDTDIR ../ APPEND earlyprintk loglevel=8 console=ttyAMA0 console=tty1 verbose \ rootwait root=/dev/mmcblk0p2 rw
LABEL fallback MENU LABEL Backup kernel LINUX ../backup/zImage FDTDIR ../backup/ APPEND earlyprintk loglevel=8 console=ttyAMA0 console=tty1 verbose \ rootwait root=/dev/mmcblk0p2 rw
(in both cases, the continuation lines are all on one line; I only split them for email purposes)