From: Joel Soete <soete.joel@scarlet.be>
To: Tejun Heo <htejun@gmail.com>
Cc: Luming Yu <luming.yu@gmail.com>, Alan Cox <alan@redhat.com>,
Ioan Ionita <opslynx@gmail.com>, Alan <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: 2.6.20-rc6 libata PATA ATAPI CDROM is not working
Date: Mon, 12 Feb 2007 20:42:27 +0000 [thread overview]
Message-ID: <45D0D133.8070801@scarlet.be> (raw)
In-Reply-To: <45CFBBD1.5090703@gmail.com>
Tejun Heo wrote:
> Please test the attached patch over 2.6.20.
>
> Thanks.
>
It's already too late so quick and dirty rebuild of 2.6.20-git6 (failled before your patch) but now your patch fixe the pb:
[snip]
ata_piix 0000:00:07.1: version 2.00ac7
ata1: PATA max UDMA/33 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14
ata2: PATA max UDMA/33 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15
scsi3 : ata_piix
ata1.00: ATA-4: QUANTUM FIREBALLlct10 15, A03.0900, max UDMA/66
ata1.00: 29336832 sectors, multi 16: LBA
ata1.00: configured for UDMA/33
scsi4 : ata_piix
ata2.01: ATAPI, max MWDMA1
ata2.01: configured for MWDMA1
scsi 3:0:0:0: Direct-Access ATA QUANTUM FIREBALL A03. PQ: 0 ANSI: 5
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdc: 29336832 512-byte hdwr sectors (15020 MB)
sdc: Write Protect is off
sdc: Mode Sense: 00 3a 00 00
SCSI device sdc: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sdc: sdc1 sdc2 < sdc5 sdc6 sdc7 sdc8 sdc9 sdc10 sdc11 sdc12 sdc13 sdc14 sdc15 >
sd 3:0:0:0: Attached scsi disk sdc
sd 3:0:0:0: Attached scsi generic sg2 type 0
scsi 4:0:1:0: CD-ROM PHILIPS CDD3610 CD-R/RW 3.09 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 6x/6x writer cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 4:0:1:0: Attached scsi CD-ROM sr0
sr 4:0:1:0: Attached scsi generic sg3 type 5
[snip]
cool ;-)
Sorry, I will try later against 2.6.20 (i guess it will also fixe the pb) and attempt to burn a cd.
I will advise you asap.
Thanks again,
Joel
next prev parent reply other threads:[~2007-02-12 20:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 23:22 2.6.19-rc5 libata PATA ATAPI CDROM SiS 5513 NOT WORKING Ioan Ionita
2006-11-16 23:50 ` Alan
2006-11-17 1:30 ` Ioan Ionita
2006-11-17 1:34 ` Ioan Ionita
2006-11-17 10:05 ` Alan Cox
2006-11-17 15:44 ` Ioan Ionita
2006-12-27 14:44 ` Joel Soete
2006-12-28 21:50 ` Joel Soete
2007-01-03 4:31 ` Tejun Heo
2007-01-03 17:19 ` Joel Soete
2007-01-27 13:22 ` 2.6.20-rc6 libata PATA ATAPI CDROM is not working Joel Soete
2007-01-27 14:10 ` Luming Yu
2007-01-27 14:42 ` Joel Soete
2007-02-12 0:58 ` Tejun Heo
2007-02-12 20:42 ` Joel Soete [this message]
2007-02-13 17:35 ` Joel Soete
2007-02-13 18:15 ` Bartlomiej Zolnierkiewicz
2007-02-13 18:34 ` Alan
2007-02-17 12:07 ` Joel Soete
2007-02-17 12:52 ` Bartlomiej Zolnierkiewicz
2007-02-13 18:22 ` Tejun Heo
2007-02-17 10:58 ` Joel Soete
2007-02-20 11:21 ` Tejun Heo
2007-02-13 19:57 ` Lennart Sorensen
2007-02-17 11:33 ` Joel Soete
2007-02-17 14:59 ` Lennart Sorensen
2007-02-17 18:26 ` Joel Soete
2007-02-21 2:55 ` Ioan Ionita
2007-02-20 7:40 Joel Soete
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=45D0D133.8070801@scarlet.be \
--to=soete.joel@scarlet.be \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luming.yu@gmail.com \
--cc=opslynx@gmail.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
Powered by JetHome