Message-ID: <426BCF6E.2000000@pobox.com>
Date: Sun, 24 Apr 2005 12:55:10 -0400
From: Jeff Garzik <jgarzik@pobox.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050328 Fedora/1.7.6-1.2.5
MIME-Version: 1.0
To: "Tais M. Hansen" <tais.hansen@osd.dk>
CC: linux-kernel@vger.kernel.org
Subject: Re: SATA/ATAPI
References: <200504211941.43889.tais.hansen@osd.dk> <200504240008.58326.tais.hansen@osd.dk>
In-Reply-To: <200504240008.58326.tais.hansen@osd.dk>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1389
Lines: 34

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/