On Wed, Sep 01, 2010, Amit Kucheria wrote:
That patch likely won't go upstream.
Why not?
OTOH, how important is support below TO3?
For Linaro, not too important I guess, some people have TO2 hardware, some Babbage 2.0 or 2.5, albeit 2.0 is not really supported anymore. EfikaMX also comes in both TO2 and TO3. Finally, some mass-market / public hardware like Sharp Netwalker are TO2 based.
TO1 won't even boot on Freescale's BSP, IIRC. AFAICT, Freescale isn't testing their BSP on TO2 if you take into account bugs like LP # 615722 [1] that caused bricking of Babbage 2.5 boards. And new HW is all TO3 and so is all known production HW. We only have a few TO2 boards now those will get rapidly get discarded when we get newer ones.
Some months back, in the beginning of this year, I heard of commercial projects targetting TO2 to save some money on the chip. There's also some mass-market / public TO2 hardware in the form of the netwalker.
So, IMHO, enable NEON support and add to release-notes that TO1/2 is not supported.
We can do that in Linaro, I'm just a bit uncomfortable that there is a non-trivial amount of TO2 devices out there, and it's a DoS issue to have this NEON flaw.
I would be ok if we would only support TO3 and the kernel wouldn't boot on TO2 hardware, but AIUI the kernel will boot just fine and turn on NEON on TO2 such as Babbage 2.x, so I'm a bit scared by just release noting it.