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 11:49:46 -0700 [thread overview]
Message-ID: <20020919114934.A27630@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
I've been doing more work on the driver. Wednesday, I was
going crazy because the data I read back from the device
was SOMETIMES NOT the same data I wrote there.
On Thursday, I switched from Linux 2.5.34 to Linux 2.5.36.
Now, the driver reads back the same data it wrote. There must
have been some bio changes in 2.5.36. 2.5.36 also
calls the driver shutdown notifier routine, which 2.5.34 didn't.
This uncovered a coding bug that causes a kernel OOPS during shutdown.
That'll be fixed in the next patch.
I'm about to test changes that put the command and status memory
mailboxes into dma memory regions. Once I've tested that,
I'll send you a new patch (Probably on Monday after week end
testing).
After that, I'll change the status reporting structures to be in dma
memory regions. Expect a patch containing that maybe the end of
next week, or the Monday following ( September 30).
> >
> > 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 18:44 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 [this message]
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
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=20020919114934.A27630@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
Powered by JetHome