James Ketrenos wrote:

Are you OK with us marking the driver as not working on big endian for 
now and getting this one fixed over time?

No.

Getting this right is a key merge requirement for all drivers.

Getting this right has also, in the past, been a proven way to find 
hidden bugs in your driver that wanted fixing anyway.

I tried reading through the thread.  From what I gathered, it sounds 
like if I want to read a value from a memory location where the adapter 
could be writing to it I would just call rmb() before I access the 
memory?  And when writing to a value, call wmb() immediately after I 
write to it?  And expunge 'volatile' from my vocabulary.

MMIO - no.  Accessors handle that for you in most cases.  For rare cases 
you might need mmiowb() or whatnot, but that is unlikely.

DMA, generally that's what people do, but it's not perfect.

	Jeff