Re: [PATCH] mvebu: Fix fixup of mbus device-tree ranges

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hallo,

On Fri, Feb 24, 2017 at 08:12:25AM +0100, Sascha Hauer wrote:
> On Wed, Feb 22, 2017 at 09:06:18PM +0100, Uwe Kleine-König wrote:
> > Commits "mvebu: {armada-370-xp,dove,kirkwood}: simplify soc init code
> > flow" simplified too much. The problem is that if the dtb used for
> > probing doesn't use the same mbus window address as barebox (i.e.
> > 0xf1000000) the fixup fails because above commits moved the information
> > about the real position to a postcore initcall which is too late because
> > the fixup happens in of_arm_init which runs as core initcall.
> 
> Said patches are currently in -next, so you could send a fixup patch
> instead or I could just remove the patches.

As the commit log isn't correct with this squashed in I sent a v2 and
not a fixup for them.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox




[Index of Archives]     [Linux Embedded]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux