but I saw only machine checks on IO accesses. When I used IO-mapped
accesses there were two addresses where the machine check happens.
With MEM-mapped accesses there was only one. So I hope the wrong
parity generation occurs only on IO-accesses (perhaps a timing problem
on the NCR chip).
> Have you tried 1.3.52 or some such? The latest ncr driver has the
> mb() instructions in the read/write macros, so it's more likely to
> work, though I haven't tried it myself.
OPTION_MEMORY_MAPPED still doesn't work in 1.3.52.
Thomas.