From: Jeff Garzik <jgarzik@pobox.com>
To: "Tais M. Hansen" <tais.hansen@osd.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA/ATAPI
Date: Sun, 24 Apr 2005 12:55:10 -0400 [thread overview]
Message-ID: <426BCF6E.2000000@pobox.com> (raw)
In-Reply-To: <200504240008.58326.tais.hansen@osd.dk>
Tais M. Hansen wrote:
> On Thursday 21 April 2005 19:41, Tais M. Hansen wrote:
>
>>One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The
>>kernel sees this drive (ata3) but apparently doesn't tie it to a sdx
>>device. The box also have a SATA harddisk, which is working just fine. The
>>relevant dmesg output is pasted below.
>
>
> I've been digging through sr, scsi, sata_via, libata-scsi and libata-core,
> littering the code with printk's.
>
> My lack of knowledge on how the kernel handles devices, is really showing now.
>
> I've been unable to figure out what is supposed to tie sr to the devices
> probed by sata_via. Also, littering sr with printk's gave me the idea that sr
> is not even looking for cdrom devices. It loads, does the basic module __init
> stuff and then silence. Should sr find devices itself or is the kernel
> supposed to inform sr via some callback hook? I could really be barking up
> the wrong tree here, and not even see it.
>
> Enabling SCSI logging and kernel debug didn't really give me anything useful.
Did you turn on ATA_ENABLE_ATAPI in include/linux/libata.h?
Jeff
next prev parent reply other threads:[~2005-04-24 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 17:41 SATA/ATAPI Tais M. Hansen
2005-04-21 23:51 ` SATA/ATAPI Brian Jackson
2005-04-22 8:50 ` SATA/ATAPI Tais M. Hansen
2005-04-22 11:14 ` SATA/ATAPI Wakko Warner
2005-04-22 11:18 ` SATA/ATAPI Tais M. Hansen
2005-04-23 22:08 ` SATA/ATAPI Tais M. Hansen
2005-04-24 16:55 ` Jeff Garzik [this message]
2005-04-24 17:16 ` SATA/ATAPI Tais M. Hansen
2005-04-26 9:46 ` SATA/ATAPI Tais M. Hansen
[not found] ` <426EAFF4.3080702@comcast.net>
2005-04-27 19:07 ` SATA/ATAPI Tais M. Hansen
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=426BCF6E.2000000@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tais.hansen@osd.dk \
/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