From: Jeff Garzik <jgarzik@pobox.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: linux-ide@vger.kernel.org,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
cova@ferrara.linux.it,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: question about SATA and IDE DVD/CD drives.
Date: Fri, 02 Jul 2004 13:02:07 -0400 [thread overview]
Message-ID: <40E5950F.2090308@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0407021745400.2190-100000@einstein.homenet>
Tigran Aivazian wrote:
> On Fri, 2 Jul 2004, Jeff Garzik wrote:
>
>>Enable CONFIG_IDE, and disable CONFIG_BLK_DEV_IDE_SATA, and that will
>>fix things I bet.
>
>
> Tried this as well on the latest snapshot (2.6.7-bk9) and it failed as
> well. Namely, SATA disk works fine but IDE subsystem doesn't see the DVD
> drive.
>
> Are you sure that I only need to enable CONFIG_IDE and not some of the
> other IDE options (disk, cdrom, chipset-specific etc)?
Sorry, I was summarizing... you definitely need a "personality" driver
such as the ide-cdrom driver in order to make use of your DVD drive.
Really, though, I need to get off my butt and finish ATAPI in libata.
Then, libata can drive PATA devices and we can get rid of all these
headaches with combined mode being split between two drivers.
I'm going to be doing some libata hacking this weekend, looking
particularly at a regression not caused by ACPI (hi Fabio). I'll see if
I can finish up ATAPI at that time.
Jeff
next prev parent reply other threads:[~2004-07-02 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 13:11 question about SATA and IDE DVD/CD drives Tigran Aivazian
2004-07-02 15:38 ` Jeff Garzik
2004-07-02 15:51 ` Tigran Aivazian
2004-07-02 15:58 ` Jeff Garzik
2004-07-02 15:55 ` James Courtier-Dutton
2004-07-02 15:56 ` Tigran Aivazian
2004-07-02 16:28 ` Tigran Aivazian
2004-07-02 16:56 ` Tigran Aivazian
2004-07-02 17:02 ` Jeff Garzik [this message]
2004-07-02 17:30 ` Tigran Aivazian
2004-07-02 18:35 ` Tigran Aivazian
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=40E5950F.2090308@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=cova@ferrara.linux.it \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
/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