[PATCH 7/7] Add more OR1k machine types and correct OR1k configure subdir

Jakob Viketoft jakob.viketoft at aacmicrotec.com
Fri Feb 19 12:52:50 UTC 2016


________________________________________
From: Sebastian Huber [sebastian.huber at embedded-brains.de]
Sent: Friday, February 19, 2016 13:36
To: Jakob Viketoft; devel at rtems.org
Subject: Re: [PATCH 7/7] Add more OR1k machine types and correct OR1k configure subdir

>On 19/02/16 10:34, Jakob Viketoft wrote:
>> diff --git a/config.sub b/config.sub
>> index 8b612ab..fbeac69 100755
>> --- a/config.sub
>> +++ b/config.sub
>> @@ -296,7 +296,7 @@ case $basic_machine in
>>       | nios | nios2 | nios2eb | nios2el \
>>       | ns16k | ns32k \
>>       | open8 \
>> -     | or1k | or32 \
>> +     | or1k | or32 | or1k-* \
>>       | pdp10 | pdp11 | pj | pjl \
>>       | powerpc | powerpc64 | powerpc64le | powerpcle \
>>       | pyramid \
>
>Why do you need this change?

We roll our own toolchain with a number of smaller changes as we need to put them in and to make that distinction clear, we have it named or1k-aac-rtems4.11-*. This is identified as the machine in RTEMS and won't map to or1k properly unless we add these extra identifiers. I pushed this in an effort to go towards more upstream, but you are right in that it's not required for the generic_or1k to build with a standard RSB toolchain.

>> @@ -1589,7 +1589,7 @@ case $basic_machine in
>>       mips*-*)
>>               os=-elf
>>               ;;
>> -     or1k-*)
>> +     or1k-* | or1k*-*-*)
>>               os=-elf
>>               ;;
>>       or32-*)
>
>This change is superfluous.

See above.


Jakob Viketoft
Senior Engineer in RTL and embedded software

ÅAC Microtec AB
Dag Hammarskjölds väg 48
SE-751 83 Uppsala, Sweden

T: +46 702 80 95 97
http://www.aacmicrotec.com



More information about the devel mailing list