[U-Boot] Regression with ubifs initialization

[Andrew Ruder <andy@aeruder.net>]

On Mon, Oct 27, 2014 at 09:45:16AM -0500, Andrew Ruder wrote:
> On Mon, Oct 27, 2014 at 03:33:00PM +0100, Wolfgang Denk wrote:
> > > It appears that 2014.10 has some issues with UBIFS initialization
> > > (details at bottom).  git-bisect results in one of the following commits
> > > being broken.  Surely it is the mtd one, but its parent commit
> > > (compat.h) does not compile.
> > 
> > Which board are you talking about?
> 
> I have a board with a PXA270 and NOR flash.  I am happy to submit the
> patches which add the board support, but they aren't really ready and
> cleaned up for submission.
> 
> > And which toolchain(s) are/have you been using to build U-Boot?
> 
> A crosstools-ng compiled gcc 4.8.2.

Wolfgang and I talked quite a bit on IRC and just catching up anyone
else looking at this with a few additional details that came out of
this.

The problem appears to stem from 'ubi part data' completing with no
errors while also not filling in any of the ubi_devices[] array.  This
in turn results in the global 'ubi' variable being NULL (on PXA270 this
is u-boot in flash).  At this point display_ubi_info() gets passed NULL
and ends up printing compiler-dependent junk for all the values.

That being said, I tried 4.9.1 and had the same issue
(display_ubi_info() being passed NULL) with different symptoms (complete
lock up because it ends up hitting data alignment issues when it starts
treating opcodes as pointers).

- Andy