On Sunday, June 05, 2011 06:30:00 AM Gordan Bobic wrote:
On 06/05/2011 12:23 PM, Peter Robinson wrote:
> On Sun, Jun 5, 2011 at 12:18 PM, Gordan Bobic<gordan(a)bobich.net> wrote:
>> On 06/05/2011 02:10 AM, Chris Tyler wrote:
>>> On Sat, 2011-06-04 at 20:53 -0400, Jon Masters wrote:
>>>> [0] We're making a "one time" incompatible ABI switch in
F-15 bringup
>>>> to the "hard float" ABI defined in section 6 of the ARM AAPCS
>>>> (commonly referred to as the ARM EABI - but that doesn't actually
>>>> exist as a name). The procedure call standard will be ARM AAPCS
>>>> vfpv3-d16, as defined in section 6 of that document. Other distros
>>>> are switching and this will form the basis of any LSB standardization
>>>> effort later on. Think of v7 and v5 as being different arches, which
>>>> they are really.
>>>
>>> And to further clarify:
>>>
>>> - This is an addition, not a switch -- the intention is to continue to
>>> support armv5tel in addition to armv7hl at this time -- Tegra and
>>> Marvell Kirkwood (including plug computer) devices which do not support
>>> armv7hl will continue to work with armv5tel.
>>>
>>> - The significant incompatibility is hardfp vs. softfp ABI (moreso than
>>> v7 vs. v5).
>>
>> So would it not be more sensible to make the distro ARMv7 without NEON?
>
> There's no mention of NEON above. Where do you get that idea from?
Chris said that Tegra wouldn't be supported on armv7hl but would
continue to work on armv5tel. The only reason why Tegra wouldn't work
with the armv7 port would be due to it's lack of NEON instructions,
since it is an armv7 processor. It was implied rather than explicit.
the stuff i have built has been hardfp with thumb vfpv3-d16 and thumb. i
setup things so you could have optional neon enabled builds.
armv7hl and armv7nhl
Dennis