>I believe changes to NCR53c80 were recently reverted back because
>these "fixes" lead to massive data corruption. It is preferable
>that the driver remains unbuildable, and therefore doesn't cause
>data corruption than to be buildable and case data corruption.
Are you talking about an event that occurred in the 2.4
tree or the 2.5 tree? Are you saying that the newer driver in
2.4 was reverted back to the older driver (i.e., the one that
is in 2.5), or are you saying that someone made some attempt
at porting the 2.5 tree's NCR53C80 driver the new DMA mapping
interface and then backed them out?
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
adam@yggdrasil.com \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/