From: Jeff Garzik <jgarzik@pobox.com>
To: Albert Lee <albertcc@tw.ibm.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
IDE Linux <linux-ide@vger.kernel.org>,
Doug Maxey <dwm@maxeymade.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: libata PATA support - work items?
Date: Tue, 04 Jan 2005 18:32:17 -0500 [thread overview]
Message-ID: <41DB2781.7000203@pobox.com> (raw)
In-Reply-To: <006301c4ee5c$49e6a230$95714109@tw.ibm.com>
Albert Lee wrote:
> The following PATA work items were previously collected from the mailing list:
> 1. ATAPI
> 1.1 possibly avoid REPORT LUNS for ATAPI devices
> 1.2 when check condition occurs, automatically request sense inside
> driver, and put that data into the sense buffer.
> 1.3 make INQUIRY report SCSI version MMC-3 (or later...)
> 1.4 support strange sector sizes
> 2. C/H/S addressing; libata currently hardcoded to use LBA
> 3. add PATA device errata/blacklist info
> (Any missing items?)
>
> Need your advice, thanks.
Yes, this seems like an accurate list to me.
I would probably prioritize #3 as the most important, followed by C/H/S
support.
Jeff
next prev parent reply other threads:[~2005-01-04 23:32 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 [this message]
2005-01-06 8:51 ` Albert Lee
2005-01-06 21:29 ` Alan Cox
2005-01-06 23:07 ` Bartlomiej Zolnierkiewicz
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=41DB2781.7000203@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=bzolnier@gmail.com \
--cc=dwm@maxeymade.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).