[U-Boot] [PATCH 0/4] dm: rpi: Move Raspberry Pi to use driver model

[Simon Glass]

Hi Stephen,

On 25 Oct 2014 23:08, "Stephen Warren" <swarren at wwwdotorg.org> wrote:
>
> On 10/25/2014 09:47 PM, Simon Glass wrote:
> > Hi Stephen,
> >
> > On Oct 25, 2014 9:43 PM, "Stephen Warren" <swarren at wwwdotorg.org
> > <mailto:swarren at wwwdotorg.org>> wrote:
> >>
> >> On 10/21/2014 08:04 PM, Simon Glass wrote:
> >> > Hi Stephen,
> >> >
> >> > On 20 October 2014 20:23, Stephen Warren <swarren at wwwdotorg.org
> > <mailto:swarren at wwwdotorg.org>> wrote:
> >> >> On 10/19/2014 09:14 PM, Simon Glass wrote:
> >> >>> Hi Stephen,
> >> >>>
> >> >>> On 17 October 2014 20:51, Stephen Warren <swarren at wwwdotorg.org
> > <mailto:swarren at 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 at wwwdotorg.org
> > <mailto:swarren at 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=351104
> >> >>
> >> >> http://elinux.org/RPi_U-Boot
> >> >>
> >> >
> >> > 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.
> >> >
> >> > Do you have your settings or images uploaded somewhere? Also please
> >> > confirm you used dm/next.
> >>
> >> FWIW, the content in the following branches does seem to work:
> >>
> >> u-boot/master
> >> 5b3ee38 kbuild: clear VENDOR variable to fix build error on tcsh
> >>
> >> u-boot-dm/master
> >> c2ded96 serial: remove uniphier_serial_initialize() call
> >>
> >
> > In what way?
>
> I ran U-Boot, and let it boot a kernel via extlinux.conf.

Ok that is probably just because I didn't pull in the patch you said was a
problem.

>
> Note that I said it worked, not that it failed.

I did misread this...

Regards,
Simon