From: Mark Lord <liml@rtr.ca>
To: Erik Slagter <erik@slagter.name>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: libata and PATA devices
Date: Tue, 09 Aug 2005 09:48:12 -0400 [thread overview]
Message-ID: <42F8B41C.4040408@rtr.ca> (raw)
In-Reply-To: <1123495856.22328.62.camel@localhost.localdomain>
Erik Slagter wrote:
>
> Is there a possibility that dell attaches PATA harddisks using a
> SATA/PATA converter to the SATA connection of the ICH6M?
That chipset is used in virtually all modern laptops,
and includes a PATA interface as well as SATA.
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.
This REALLY ought to be on by default now, Jeff.
Especially since the default is to NOT work at all..
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.
The best way to get any remaining kinks out of it would be to
release it to a much wider audience.
As is, it's pretty good, except for the broken libata error handling
that (by default) locks up machines every hour or two. But there's
also a fix for that, again floating around only in private repositories.
Let's get more of this code out where it can be used, guys!
Cheers
next prev parent reply other threads:[~2005-08-09 13:48 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 [this message]
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
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=42F8B41C.4040408@rtr.ca \
--to=liml@rtr.ca \
--cc=erik@slagter.name \
--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).