Here's my latest progress on my changes to the DAC960 driver.
I spent Tuesday banging my head trying to figure out why data blocks
written to disk to SOMETIMES were read back with DIFFERENT data.
On wednesday, I changed from using Linux 2.5.34 to using Linux 2.5.36.
My bad data problem went away with that change. There must have been
an important change in the 2.5.36 BIO code.
However, this change uncovered a yank-put error in my version of the
driver's shutdown notification function. The version I mailed you will
print out messages about "bad dma" when you try to shutdown.
That code is freeing some dma structures to the wrong dma pool.
Apparently Linux 2.5.34 never called that function.
I'm about to test changes to put the command and status mailboxes
into dma memory regions. I'll run some tests on it
over the week end, and mail you a new set of changes on Monday.
Let me know how it goes.
On Mon, Sep 16, 2002 at 10:26:23PM +0200, Daniel Phillips wrote:
> > I have the DAC960 driver working in 2.5.34. The work isn't
> > complete yet. But, I'm able to boot, and do mke2fs
> > on partitions on logical drives, and then do e2fsck
> > on those partitions. It seems to work, although more
> > testing is required. Is there any interest in reviewing
> > the code so far, or should I continue testing and complete
> > the remaining issues first?
> Please post the patch, I'll try it right away.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:27 EST