public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tais M. Hansen" <tais.hansen@osd.dk>
To: linux-kernel@vger.kernel.org
Cc: Jeff Garzik <jgarzik@pobox.com>
Subject: Re: SATA/ATAPI
Date: Sun, 24 Apr 2005 19:16:30 +0200	[thread overview]
Message-ID: <200504241916.34726.tais.hansen@osd.dk> (raw)
In-Reply-To: <426BCF6E.2000000@pobox.com>

[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]

On Sunday 24 April 2005 18:55, Jeff Garzik wrote:
> > 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?

Tried with it both defined and undefined. When it's defined an extra line is 
added (the last one below) when loading the sata_via module:

sata_via version 1.1
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 20
sata_via(0000:00:0f.0): routed to hard irq line 4
ata3: SATA max UDMA/133 cmd 0xE800 ctl 0xE402 bmdma 0xD400 irq 20
ata4: SATA max UDMA/133 cmd 0xE000 ctl 0xD802 bmdma 0xD408 irq 20
ata3: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 
88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_via
ata4: no device found (phy stat 00000000)
scsi3 : sata_via
ata3: command 0xa0 timeout, stat 0xd0 host_stat 0x1

-- 
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-04-24 17:16 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   ` SATA/ATAPI Jeff Garzik
2005-04-24 17:16     ` Tais M. Hansen [this message]
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=200504241916.34726.tais.hansen@osd.dk \
    --to=tais.hansen@osd.dk \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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