On Wednesday, 21 September 2016 15:14:41 BST Daniel Schwierzeck wrote:
> Hi Paul,
>
> Am 21.09.2016 um 12:08 schrieb Paul Burton:
> > Some systems are configured such that multiple CPUs begin running from
> > their reset vector following a system reset. If this occurs then U-Boot
> > will be run o
On Wednesday, 21 September 2016 12:59:39 BST Langer, Thomas wrote:
> Hello Paul,
>
> > diff --git a/arch/mips/cpu/start.S b/arch/mips/cpu/start.S
> > index fc6dd66..dd37ac3 100644
> > --- a/arch/mips/cpu/start.S
> > +++ b/arch/mips/cpu/start.S
> > @@ -112,6 +112,31 @@ ENTRY(_start)
> >
> > .a
Hi Paul,
Am 21.09.2016 um 12:08 schrieb Paul Burton:
> Some systems are configured such that multiple CPUs begin running from
> their reset vector following a system reset. If this occurs then U-Boot
> will be run on multiple CPUs simultaneously, which causes all sorts of
> issues as the multiple
Hello Paul,
>
> diff --git a/arch/mips/cpu/start.S b/arch/mips/cpu/start.S
> index fc6dd66..dd37ac3 100644
> --- a/arch/mips/cpu/start.S
> +++ b/arch/mips/cpu/start.S
> @@ -112,6 +112,31 @@ ENTRY(_start)
>
> .align 4
> reset:
> +#if __mips_isa_rev >= 6
> + .setpush
> + .set
Some systems are configured such that multiple CPUs begin running from
their reset vector following a system reset. If this occurs then U-Boot
will be run on multiple CPUs simultaneously, which causes all sorts of
issues as the multiple instances of U-Boot clobber each other.
Prevent this from hap
5 matches
Mail list logo