From: Dave Olien <dmo@osdl.org>
To: Daniel Phillips <phillips@arcor.de>
Cc: Jens Axboe <axboe@suse.de>, Samium Gromoff <_deepfire@mail.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [2.5] DAC960
Date: Thu, 19 Sep 2002 14:25:05 -0700 [thread overview]
Message-ID: <20020919142505.B27767@acpi.pdx.osdl.net> (raw)
In-Reply-To: <E17r2Rr-0001Vk-00@starship>; from phillips@arcor.de on Mon, Sep 16, 2002 at 10:26:23PM +0200
Daniel
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.
Thanks!
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.
>
> --
> Daniel
next prev parent reply other threads:[~2002-09-19 21:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 5:30 Samium Gromoff
2002-09-10 6:20 ` Jens Axboe
2002-09-10 16:16 ` Dave Olien
2002-09-15 4:21 ` Daniel Phillips
2002-09-15 13:19 ` Jens Axboe
2002-09-15 15:23 ` Daniel Phillips
2002-09-15 16:18 ` Daniel Phillips
2002-09-16 20:13 ` Dave Olien
2002-09-16 20:26 ` Daniel Phillips
2002-09-16 22:08 ` Dave Olien
2002-09-16 22:25 ` Dave Olien
2002-09-19 18:49 ` Dave Olien
2002-09-19 19:16 ` Daniel Phillips
2002-09-19 22:09 ` Dave Olien
2002-09-19 22:21 ` Daniel Phillips
2002-09-20 6:21 ` Jens Axboe
2002-09-20 21:32 ` Daniel Phillips
2002-09-19 21:25 ` Dave Olien [this message]
2002-09-20 6:20 ` Jens Axboe
2002-09-15 15:14 ` Alan Cox
2002-09-15 16:20 ` Daniel Phillips
2002-09-18 16:17 James Bottomley
2002-09-18 16:40 ` Daniel Phillips
2002-09-23 19:23 Dave Olien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020919142505.B27767@acpi.pdx.osdl.net \
--to=dmo@osdl.org \
--cc=_deepfire@mail.ru \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®