All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	albertcc@tw.ibm.com
Subject: libata PATA to-do list
Date: Wed, 13 Oct 2004 15:44:13 -0400	[thread overview]
Message-ID: <416D858D.2000702@pobox.com> (raw)
In-Reply-To: <200410110045.05952.bzolnier@elka.pw.edu.pl>


Since Bart was asking about to-do items for ATAPI (a key requirement for 
useful PATA support), I thought I would go ahead and post the main PATA 
to-do items, should anybody like to work on these.

* ATAPI (to-do list outlined in recent conversation with Bart)
* C/H/S addressing; libata currently hardcoded to use LBA
* add PATA device errata/blacklist info; Alan likes to complain about 
this one, with colorful examples of device death :)

There may be one or two minor things I am forgetting, but those are the 
main ones.

	Jeff




           reply	other threads:[~2004-10-13 19:44 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200410110045.05952.bzolnier@elka.pw.edu.pl>]

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=416D858D.2000702@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertcc@tw.ibm.com \
    --cc=bzolnier@elka.pw.edu.pl \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.