Jeff Garzik wrote:
> Assumptions or not, we have a standard way of documenting these
> assumptions in the source code... __be32 and cpu_to_be32() do the right
> thing (become no-ops) on BE, while ensuring that we can continue to use
> valuable source checking tools. If the Cell drivers ever need to work
> on LE, then all the better -- the driver automatically works there.
The point that Jens was trying to make is that the chip is designed
to be native-endian and our firmware switches it into big-endian
mode for us.
I know that at least one other system exists that uses the same
chip on a little-endian CPU and I'm pretty sure that they don't set
it to BE then, so using __be32 will actually break the driver for that
system.
Arnd <><
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
