From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Albert Lee <albertcc@tw.ibm.com>
Subject: Re: PATA drivers in libata?
Date: Sun, 13 Feb 2005 22:38:47 +0000 [thread overview]
Message-ID: <1108334326.19353.20.camel@localhost.localdomain> (raw)
In-Reply-To: <420FA1B9.6030100@pobox.com>
On Sul, 2005-02-13 at 18:51, Jeff Garzik wrote:
> libata-dev now has two drivers that support PATA, pata_pdc2027x and
> ata_piix, and the core is getting close (DMA blacklist in, C/H/S support
> close).
Do you have DMA change down sorted - CRC error, drop speed and/or switch
to PIO then later flip back. Thats one real horror to get right and one
thats badly screwy in the current IDE code (-ac IDE can hang the box for
ages, base will sometimes crash)
> * With ATA passthru (in libata-dev currently), libata supports SMART and
> the HDIO_CMD/HDIO_TASK generalized ioctls. Should I care about
> supporting other ioctls?
I'd rather the libata driver just had the sane ioctls
> * pci_enable_device() issues?
Nothing really special there, pci_disable_device can be funny thats all.
> * power management differences?
AFAIK only the "I have a cache but no flush command" issue
I'm all for burying the old IDE layer
next prev parent reply other threads:[~2005-02-13 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 18:51 PATA drivers in libata? Jeff Garzik
2005-02-13 21:12 ` Mark Hahn
2005-02-13 22:01 ` Jeff Garzik
2005-02-14 0:19 ` Doug Maxey
2005-02-14 0:25 ` Jeff Garzik
2005-02-13 22:38 ` Alan Cox [this message]
2005-02-14 0:16 ` Jeff Garzik
2005-02-14 20:42 ` Alan Cox
2005-02-17 1:13 ` Benjamin Herrenschmidt
2005-02-17 1:11 ` Benjamin Herrenschmidt
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=1108334326.19353.20.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=albertcc@tw.ibm.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