From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Albert Lee <albertcc@tw.ibm.com>, Jeff Garzik <jgarzik@pobox.com>,
IDE Linux <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@maxeymade.com>
Subject: Re: libata PATA support - work items?
Date: Fri, 7 Jan 2005 00:07:34 +0100 [thread overview]
Message-ID: <58cb370e050106150743d6271f@mail.gmail.com> (raw)
In-Reply-To: <1105044491.24187.268.camel@localhost.localdomain>
On Thu, 06 Jan 2005 21:29:42 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Iau, 2005-01-06 at 08:51, Albert Lee wrote:
> > For the 1st item,
> > - add PATA device errata/blacklist info
> > Is there any detail or draft design idea available?
>
> There is a fair bit of code in drivers/ide. Most of it is handling drive
> problems that occurred with early DMA drives and it uses the
> model/firmware info in the ident string to match drives that claim to do
> DMA but do not and drives that claim not to but can.
>
> The logic is fairly simple and the database is easily transported or
> shared. It is fairly important because some of these old drives
> corrupted data if used DMA. (see drivers/ide/ide-dma.c)
>
> For PIO problem drives where there is a need to keep PIO modes chosen
> carefully then ide-lib has a list (ide_pio_blacklist) and the ide-io
> code knows about pio modes and older style EIDE cycle timing reports
> (ide_get_best_pio_mode)
There was some rumor (?) that this blacklist was created on CMD640
controller programmed with wrong timings...
BTW ide_get_best_pio_mode(), it is really misleading
(i.e. recent PIO tuning bug in it821x.c).
> IDE CD has some DMA blacklists for ATAPI but they should be viewed with
> caution as many entries were due to a bug in our atapi implementation
> that was fixed long ago.
There is only a common DMA blacklist in ide-dma.c.
prev parent reply other threads:[~2005-01-06 23:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 10:42 libata PATA support - work items? Albert Lee
2005-01-01 19:19 ` Eric Mudama
2005-01-03 20:56 ` Greg Freemyer
2005-01-03 21:20 ` Eric Mudama
2005-01-03 22:09 ` Bartlomiej Zolnierkiewicz
2005-01-04 23:43 ` Jeff Garzik
2005-01-04 23:41 ` Jeff Garzik
2005-01-05 0:50 ` Alan Cox
2005-01-05 2:42 ` Jeff Garzik
2005-01-05 3:43 ` Alan Cox
2005-01-05 12:59 ` Bartlomiej Zolnierkiewicz
2005-01-04 23:32 ` Jeff Garzik
2005-01-06 8:51 ` Albert Lee
2005-01-06 21:29 ` Alan Cox
2005-01-06 23:07 ` Bartlomiej Zolnierkiewicz [this message]
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=58cb370e050106150743d6271f@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=dwm@maxeymade.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).