[PATCH 0/9] Switch internal registers address to 0xF1 on Armada 370/XP

[Jason Cooper]

On Wed, May 22, 2013 at 08:05:13PM +0200, Thomas Petazzoni wrote:
> Dear Jason Cooper,
> 
> On Wed, 22 May 2013 13:13:59 -0400, Jason Cooper wrote:
> 
> > > On Wed, 22 May 2013 12:49:36 -0400, Jason Cooper wrote:
> > > 
> > > > > As far as I know, a DT-capable bootloader doesn't pass any ATAG. The
> > > > > ARM register that was used to pass the pointer to the ATAGS is now used
> > > > > to pass the pointer to the DTB in memory.
> > > > 
> > > > So we could look for the ATAG magic or the dtb magic at that address,
> > > > then we know if we have an old or new bootloader...
> > > 
> > > No, because you can use an old bootloader, and still do some old-style
> > 
> > Did you mean 'new bootloader'?
> 
> Gaah, yes, of course. Getting myself confused with all this old/new
> discussion :)
> 
> "No, because you can use a new bootloader, and still do some
> old-style..."
> 
> > > appended-DTB booting, in which case you have a new bootloader
> > > (registers mapped at 0xf1), but you see the ATAG magic, which will make
> > > you think you booted from an old bootloader (registers mapped at 0xd0).
> > > 
> > > For example, I'm currently booting alternatively with an old and a new
> > > bootloader (to test that things work properly), and in both cases I'm
> > > booting old style, DTB-appended, with ATAGs.
> > 
> > Is this something users would experience?  I think it is fairly safe to
> > say that once dt-able bootloaders are shipped, they will provide a dtb.
> > So, OF_DT_MAGIC == new bootloader might hold true for users.
> 
> We could be tempted to say that, but since what users trying to do this
> would experience is a completely silent kernel, no message, nothing,
> I'm not sure I like this too much.

Ok, I buy that.  Having stared at blank terminals many times, that's
not cool. :(  It really hurts to hear the HD spin down too.  It just
sounds like something died a horrible agonizing death.

thx,

Jason.