From: Erik Slagter <erik@slagter.name>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Mark Lord <liml@rtr.ca>, linux-ide@vger.kernel.org
Subject: Re: libata and PATA devices
Date: Thu, 11 Aug 2005 11:37:31 +0200 [thread overview]
Message-ID: <1123753051.4226.22.camel@localhost.localdomain> (raw)
In-Reply-To: <42FACCA8.6050408@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
On Wed, 2005-08-10 at 23:57 -0400, Jeff Garzik wrote:
> > Most current laptops ship with a PATA hard drive, and a PATA
> > ATAPI drive. The easiest way to make them usable under Linux-2.6
> > is to patch libata and turn on ATAPI support, using ata_piix.
>
> No, the best thing to do is use the IDE driver for PATA. That is the
> most stable, most well-tested path to ATAPI support at present.
>
> > This REALLY ought to be on by default now, Jeff.
> > Especially since the default is to NOT work at all..
>
> Correct, because currently no one should be using libata for PATA support.
You are sort of contradicting yourself. My setup (Dell laptop with ICH6M
and PATA harddisk) defaults to using libata for the PATA hardisk. Only
with a specific patch (which adds the PCI id to the IDE driver's id
list, and which was not quite accepted here) the IDE driver will
recognise the ICH6M and use it (and then it works fine).
> Turning on ATAPI and PATA support by default will break existing setups.
> > The libata code is taking forever to catch up to modern reality,
> > mostly because so much of it lives eternally in Jeff's private
> > git repository, where only a few people ever exercise the code.
>
> Exaggeration. We're talking about a single #define here, to enable ATAPI.
How about a simple configure option...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-11 9:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 17:48 libata and PATA devices Andreas Klöckner
2005-08-08 1:43 ` Tejun Heo
2005-08-08 3:02 ` Jeff Garzik
2005-08-08 10:10 ` Erik Slagter
2005-08-09 13:48 ` Mark Lord
2005-08-09 14:10 ` Mark Lord
2005-08-09 18:01 ` Jeff Garzik
2005-08-09 17:05 ` Erik Slagter
2005-08-09 18:02 ` Jeff Garzik
2005-08-09 17:59 ` Jeff Garzik
2005-08-11 3:57 ` Jeff Garzik
2005-08-11 9:37 ` Erik Slagter [this message]
2005-08-11 10:03 ` Bartlomiej Zolnierkiewicz
2005-08-11 10:17 ` Erik Slagter
2005-08-11 10:26 ` Bartlomiej Zolnierkiewicz
2005-08-11 15:29 ` Erik Slagter
2005-08-11 15:57 ` Bartlomiej Zolnierkiewicz
2005-08-11 16:48 ` Erik Slagter
2005-08-11 17:05 ` Mark Lord
2005-08-11 17:19 ` Jeff Garzik
2005-08-11 19:38 ` Erik Slagter
2005-08-11 20:19 ` Wes Newell
2005-08-11 20:21 ` Jeff Garzik
2005-08-11 20:25 ` Jeff Garzik
2005-08-13 11:30 ` Erik Slagter
2005-08-13 15:33 ` Jeff Garzik
2005-08-13 15:50 ` Erik Slagter
2005-08-13 15:56 ` Jeff Garzik
2005-08-13 16:03 ` Erik Slagter
2005-08-13 16:44 ` Jeff Garzik
2005-08-13 16:53 ` Erik Slagter
2005-08-15 21:39 ` Mark Lord
2005-08-16 7:21 ` Erik Slagter
2005-08-13 15:56 ` Tyler
2005-08-13 15:57 ` Jeff Garzik
2005-08-13 16:05 ` Erik Slagter
2005-08-13 16:42 ` Jeff Garzik
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=1123753051.4226.22.camel@localhost.localdomain \
--to=erik@slagter.name \
--cc=jgarzik@pobox.com \
--cc=liml@rtr.ca \
--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).