2014-11-05 0:36 GMT+01:00 Michael Schmitz <schmitzmic@xxxxxxxxx>:
Hi Finn,
Thanks for testing.
"No regressions over v1" means "no regressions", right?
Well, what would I compare the driver performance to? With your patches to
sort out locking races, the driver is more stable than I've ever seen it in
years. That's a definite win. Big improvement over the driver in its current
state in m68k and mainstream (which locks up quite reliably with even
moderate concurrent IDE and SCSI I/O for me). No regression over v1 or
patches that you sent for me to test off-list.
On the other hand, I've seen warnings about lost bytes (stuck in the DMA
fifo) for the first time _ever_ with the new driver - we've discussed that
at length, and it is still unclear why these happen. This is a known NCR5380
issue, and pretty much anything could have precipitated that. Must have
happened for other Falcon users before in the past, because the interrupt
handler explicitly checks for this condition.
Do you know about the Falcon's disturbance in the SDMA clock signal
hardware problem?
Most Falcons, specially those used in music studios, have a hardware
patch to fix this, it's normally called SCSI patch.
Some more info:
http://didierm.pagesperso-orange.fr/doc/eng/c_0a.htm
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
