From: Brian Jackson <notiggy@gmail.com>
To: "Tais M. Hansen" <tais.hansen@osd.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA/ATAPI
Date: Thu, 21 Apr 2005 18:51:09 -0500 [thread overview]
Message-ID: <fb20c2140504211651134980d9@mail.gmail.com> (raw)
In-Reply-To: <200504211941.43889.tais.hansen@osd.dk>
Just to check, you do have scsi cdrom support enabled right?
On 4/21/05, Tais M. Hansen <tais.hansen@osd.dk> wrote:
> Hi,
>
> I know there has been some talking about SATA/ATAPI being experimental and
> might not work at all under kernel-2.6.x.
>
> 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.
>
> Is there anything I can do to help the development of SATA/ATAPI devices?
>
> libata version 1.10 loaded.
> sata_promise version 1.01
> ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 18 (level, low) -> IRQ 18
> ata1: SATA max UDMA/133 cmd 0xF8804200 ctl 0xF8804238 bmdma 0x0 irq 18
> ata2: SATA max UDMA/133 cmd 0xF8804280 ctl 0xF88042B8 bmdma 0x0 irq 18
> ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003
> 88:407f
> ata1: dev 0 ATA, max UDMA/133, 240121728 sectors:
> ata1: dev 0 configured for UDMA/133
> scsi0 : sata_promise
> ata2: no device found (phy stat 00000000)
> scsi1 : sata_promise
> Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
> Type: Direct-Access ANSI SCSI revision: 05
> 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
> SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB)
> SCSI device sda: drive cache: write back
> SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB)
> SCSI device sda: drive cache: write back
> sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
> Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
>
> --
> 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)
>
>
>
next prev parent reply other threads:[~2005-04-21 23:51 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 ` Brian Jackson [this message]
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 ` 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=fb20c2140504211651134980d9@mail.gmail.com \
--to=notiggy@gmail.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