From: Tejun Heo <htejun@gmail.com>
To: "Andreas Klöckner" <inform@tiker.net>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org
Subject: Re: libata and PATA devices
Date: Mon, 08 Aug 2005 10:43:41 +0900 [thread overview]
Message-ID: <42F6B8CD.4050100@gmail.com> (raw)
In-Reply-To: <200508071949.03782.inform@tiker.net>
Hello, Andreas.
Andreas Klöckner wrote:
> Hey Jeff, all,
>
> I was wondering why ATA_ENABLE_PATA and ATA_ENABLE_ATAPI are #undef'ed in
> include/linux/libata.h by default, since reverting them to #define's was the
> only way to make the ata-piix driver detect my CDROM on my new shiny ThinkPad
> (Intel Corp. 82801FBM (ICH6M) SATA Controller). I would assume that most
> people would want this. The drive worked out of the box on Ubuntu, so I
> assume that their vendor patch includes this anyway.
>
> Is there a specific reason that these are disabled? Are there any bad
> consequences that I'm not aware of? Only reading the source really revealed
> that this was the way to get my CD-ROM to work.
SATA ATAPI support still has some issues, but as you can read from the
following post, libata is almost there now.
http://marc.theaimsgroup.com/?l=linux-kernel&m=112261379120567&w=2
I don't know much about PATA support. All I know is that ICH's seem
to generate a lot of noise in this mailing list w/ its legacy, combined,
ahci and whatever modes and no one setting seems to satisfy all. (If
anyone knows more about it, please fill in here.)
--
tejun
next prev parent reply other threads:[~2005-08-08 1:43 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 [this message]
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
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=42F6B8CD.4050100@gmail.com \
--to=htejun@gmail.com \
--cc=inform@tiker.net \
--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).