Re: evbarm-earmv6hf in qemu

[Brad Spencer <brad%anduin.eldar.org@localhost>]

matthew green <mrg%eterna23.net@localhost> writes:

> minor point, not really related to the main subject:
>
>> ----
>> include "arch/evbarm/conf/GENERIC"
>>
>> makeoptions     CPUFLAGS="-mcpu=cortex-a7 -mfpu=neon"
>
> this cpu choice is odd to me - A7 is a armv7 cpu, not armv6.
>
>
> .mrg.


Yes...  you have to do it that way to be able to use the UEFI boot from
the armv7 image.  I doubt that a v6 CPU will actually work and I don't
think that it will actually build ...  you can try it by building a
GENERIC arm kernel using the v6 tool chain.  I know that nbconfig will
work, but I don't think it will survive the compile (I have totally
forgotten why... but I did try this some time ago).

This literally is no different than what the RPI2 kernel does when you
build earmv6hf and use it on a RPI2 or RPI3.  You use the v6 tool chain
for that build and tell it that the CPU is a v7 CPU.





-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org