OMAP baseline test results for v3.10-rc6

Paul Walmsley paul at pwsan.com
Mon Jul 29 04:29:44 EDT 2013


Hi

On Wed, 26 Jun 2013, Tom Rini wrote:

> On 06/26/2013 01:19 PM, Paul Walmsley wrote:
> > On Tue, 25 Jun 2013, Tom Rini wrote:
> > 
> >> On 06/25/2013 02:20 PM, Paul Walmsley wrote:
> >>
> >>> BeagleBone-white has the additional complication that it is not easy 
> >>> to automate, due to the way that power is delivered to the board, so 
> >>> there is an extra dimension of difficulty there.
> >>
> >> Ah-ha, I reproduced your failure.  If I make up a concat uImage + DTB,
> >> rather than pass them separately, it fails to boot.  If you switch to
> >> mainline U-Boot (v2012.10 or later) you get support for separate image +
> >> dtb (v2013.04 gives you bootz and zImage support).
> > 
> > Yeah, I've tried to keep the original bootloader that came on the first SD 
> > card image that was used on that device.  But am starting to think that 
> > it's time to stop my bootloader independence jihad, since appended DTB 
> > booting is so broken - have seen similar problems on SoCs from other 
> > vendors as well :-(
> 
> Well, me?  I'm all in favor of people using latest release of U-Boot for
> their board and yelling and screaming (or just reporting bugs) when
> things don't work.  I'm biased of course.

That's exactly how bootloader developers should be testing their changes.  
But most of the rest of us kernel folks don't want to deal with constantly 
replacing bootloaders, and then dealing with the inevitable bootloader 
regressions, when what we're really trying to test is the kernel...
The kernel should be completely independent of the bootloader used.  

> And assuming rmk answers the way I expect he will, like it or not, the 
> version(s) we kit up and get in the box need to be factored into our 
> test system setup so if folks don't want to avail themselves of 
> improvements, they still get a functional system too.

Yep seems like a good idea from a customer service point of view.  Also 
most OMAP devices out there probably have locked bootloaders, so replacing 
the bootloader is often not an option.


- Paul



More information about the linux-arm-kernel mailing list