On Thu, Aug 13, 2015 at 07:48:30PM +1000, Jonathan Gray wrote:
> I would be curious to see what happens when running a recent u-boot
> and the following:
> 
> Index: armv7_machdep.c
> ===================================================================
> RCS file: /cvs/src/sys/arch/armv7/armv7/armv7_machdep.c,v
> retrieving revision 1.24
> diff -u -p -r1.24 armv7_machdep.c
> --- armv7_machdep.c   19 May 2015 03:30:54 -0000      1.24
> +++ armv7_machdep.c   13 Aug 2015 09:36:53 -0000
> @@ -397,6 +397,12 @@ initarm(void *arg0, void *arg1, void *ar
>           bus_space_handle_t *);
>  
>       board_id = (uint32_t)arg1;
> +     /*
> +      * u-boot has decided the top four bits are
> +      * 'compatibility revision' for sunxi
> +      */
> +     if (board_id != 0xffffffff)
> +             board_id &= 0x0fffffff;
>  
>       /*
>        * Heads up ... Setup the CPU / MMU / TLB functions
> 

Tested your patch with Banana Pi and it doesn't work. Without the
workaround option to boot older kernels, it won't boot with U-Boot
2015.10-rc1.

It does, however, works OK with the workaround, as does -current.

-- 
db

Reply via email to