From: Daniel Phillips <phillips@arcor.de>
To: Dave Olien <dmo@osdl.org>
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 21:16:53 +0200 [thread overview]
Message-ID: <E17s6nH-0000xq-00@starship> (raw)
In-Reply-To: <20020919114934.A27630@acpi.pdx.osdl.net>
On Thursday 19 September 2002 20:49, Dave Olien wrote:
> 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 was in the process of writing to you as this one came in...
I have booted 2.5.34 and 2.5.36, the same controller as yours, on my dual
PIII box and it is apparently functioning well. I have not done any kind
of load testing yet.
Congratulations! I presume you are now the DAC960 maintainer, subject to
approval from on high of course, and assuming you are willing. I'd like
to do some spelling changes, just obvious ones for now, like removing
spelling wrappers from standard kernel interfaces. Want patches?
--
Daniel
next prev parent reply other threads:[~2002-09-19 19:11 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 [this message]
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=E17s6nH-0000xq-00@starship \
--to=phillips@arcor.de \
--cc=_deepfire@mail.ru \
--cc=axboe@suse.de \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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®