On 2 November 2016 at 19:36, Andre Przywara wrote:
> At the moment we use the arch/arm directory for arm64 boards as well,
> so the Makefile will pick up the "arm" name for the architecture to use
> for tagging binaries in U-Boot image files.
> Differentiate between the two by looking at the CPU v
Hi,
On 03/11/16 09:10, Alexander Graf wrote:
> On 11/03/2016 10:08 AM, Andre Przywara wrote:
>> Hi,
>>
>> On 03/11/16 08:54, Alexander Graf wrote:
>>> On 11/03/2016 02:36 AM, Andre Przywara wrote:
At the moment we use the arch/arm directory for arm64 boards as well,
so the Makefile will
On 11/03/2016 10:08 AM, Andre Przywara wrote:
Hi,
On 03/11/16 08:54, Alexander Graf wrote:
On 11/03/2016 02:36 AM, Andre Przywara wrote:
At the moment we use the arch/arm directory for arm64 boards as well,
so the Makefile will pick up the "arm" name for the architecture to use
for tagging bin
Hi,
On 03/11/16 08:54, Alexander Graf wrote:
> On 11/03/2016 02:36 AM, Andre Przywara wrote:
>> At the moment we use the arch/arm directory for arm64 boards as well,
>> so the Makefile will pick up the "arm" name for the architecture to use
>> for tagging binaries in U-Boot image files.
>> Differe
On 11/03/2016 02:36 AM, Andre Przywara wrote:
At the moment we use the arch/arm directory for arm64 boards as well,
so the Makefile will pick up the "arm" name for the architecture to use
for tagging binaries in U-Boot image files.
Differentiate between the two by looking at the CPU variable bein
At the moment we use the arch/arm directory for arm64 boards as well,
so the Makefile will pick up the "arm" name for the architecture to use
for tagging binaries in U-Boot image files.
Differentiate between the two by looking at the CPU variable being defined
to "armv8", and use the arm64 architec
6 matches
Mail list logo