From: Dave Olien <dmo@osdl.org>
To: Samium Gromoff <_deepfire@mail.ru>
Cc: cobra@compuserve.com, alan@lxorguk.ukuu.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: DAC960 at 2.5.50
Date: Tue, 3 Dec 2002 11:42:01 -0800 [thread overview]
Message-ID: <20021203114201.A32313@acpi.pdx.osdl.net> (raw)
In-Reply-To: <E18HR1a-0005QL-00@f12.mail.ru>; from _deepfire@mail.ru on Thu, Nov 28, 2002 at 06:56:22PM +0300
Let me know if you find any problems at all. I'll try to
address them.
I think the biggest "imperfection" is just the coding style of
the whole driver. I might submit some patches over time to clean
up coding style.
The next problem is that it doesn't handle media errors yet.
If you have a read or write failure because a sector on your disk
is bad, it fails the entire read or write. With all the coalescing
of requests that the block layer does, this might fail ALL of a
really large transfer just because one sector is bad.
I'm working on a patch that retries failures section at a time,
so that the failure will be more closely limited to the sector
that is bad.
On Thu, Nov 28, 2002 at 06:56:22PM +0300, Samium Gromoff wrote:
> > Samium Gromoff...
> > > > <alan@lxorguk.ukuu.org.uk>
> > > > [PATCH] update to OSDL DAC960 driver
> > > >
> > > > Its not perfect but it works
> > > is it supposed to blow my data, or is it relatively safe to use?
> >
> > There have been a few poeple using this patch for about 5 versions of
> > 2.5 so far. I haven't done heavy testing myself, just booting and doing
> > some other testing of modules and drivers. I am running the DAC960 on
> > my root/boot filesystem and haven't seen any problems yet.
> thank you. i`ll join the 2.5 DAC user crowd soon then :-)
>
> ---
> regards,
> Samium Gromoff
> _____________________________________
>
> -
> 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/
next prev parent reply other threads:[~2002-12-03 19:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 15:56 DAC960 at 2.5.50 Samium Gromoff
2002-12-03 19:42 ` Dave Olien [this message]
2002-12-04 6:57 ` Samium Gromoff
2002-12-05 12:17 ` Monitor utility (was Re: DAC960 at 2.5.50) Kevin Brosius
2002-12-05 13:06 ` Samium Gromoff
2002-12-05 16:22 ` Randy.Dunlap
2002-12-05 17:45 ` Dave Olien
2002-12-05 19:21 ` Mihai RUSU
2002-12-05 21:33 ` Dave Olien
-- strict thread matches above, loose matches on Subject: below --
2002-11-28 15:34 DAC960 at 2.5.50 Kevin Brosius
2002-11-28 14:19 Samium Gromoff
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=20021203114201.A32313@acpi.pdx.osdl.net \
--to=dmo@osdl.org \
--cc=_deepfire@mail.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cobra@compuserve.com \
--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