On Mon, Oct 31, 2011 at 04:04:17AM -0400, Joshua Kinard wrote: > A.k.a., Tulip (and possibly ThunderLAN) assume little-endian, when we're > talking big-endian archs here. Interesting. Simple fix, as in defining a > few driver structures with little- and big-endian versions (if they're doing > something like packing bits or using bitfields)? Or is it more complex than > that? iirc, the PCI bridge on the cards do 32bit swaps (address invariant) so tulip chips need to run in big endian mode, which in turn makes descriptors also big endian. But none of the tulip driver supports big endian descriptors. That's fixable of course. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
