From: Luke Ross <luke@lukeross.name>
To: Tejun Heo <tj@kernel.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes 2/2] libata: implement ATAPI_HORKAGE_NOPIO and apply it to GGW-H10N
Date: Tue, 17 Jun 2008 05:54:39 -0400 [thread overview]
Message-ID: <20080617095439.GA9359@lukeross.name> (raw)
In-Reply-To: <48578080.5030605@kernel.org>
Hi,
On Tue, Jun 17, 2008 at 06:14:40PM +0900, Tejun Heo wrote:
> Alan Cox wrote:
> > On Tue, 17 Jun 2008 12:37:24 +0900
> > Tejun Heo <tj@kernel.org> wrote:
> >
> >> LG blueray drive GGW-H10N can't do ATAPI PIO. Implement
> >> ATAPI_HORKAGE_NOPIO and apply it to the drive. If the horkage is
> >> active, atapi_check_dma() always returns 0 and warns if the controller
> >> needs ATAPI PIO for certain commands.
> >
> > This all seems wildly improbable as a drive with such a bug would not
> > appear to be going to work in Windows. I'd like to know more and see more
> > than one bug report for that drive before it goes in
> >
> > You might even be looking at a single drive with a one off wiring flaw or
> > chip fault at this point.
>
> I thought it was improbable too but it's a brand new relatively cheap
> blueray writer so it's quite possible that they screwed up the firmware
> on this one as are often the cases for first gen devices.
>
> Relatively cheap it may be, it's still around $300, so I don't think
> I'll get one for testing. The high price could probably explain low
> error report rate.
>
> Luke, what happens if you use the drive on windows? Does it just work?
Sorry, I've a Windows-free household and the machines a self-build so
doesn't come with a license. I'll see if I can find a solution but it
may take a little while.
It could be a drive fault or it could be a funky issue with the
drive/controller combination. nvidia claimed they weren't aware of any
problems with the device on the nForce chipset (LG didn't bother
responding to my email). It is LG's first Blu-Ray/HD-DVD combo drive and
I did buy it shortly after UK release so it could be an early build.
I've run it with firmwares 1.01 to 1.04.
Originally the drive was bought for a different PC with a Silicon Image
3114 controller. The drive worked fine with this (sata_sil). Then I
changed to the nForce motherboard and it never worked with the mobo
(AHCI driver/AHCI mode in BIOS). However it does work on a Silicon Image
3512 PCI card (sata_sil again) in the same machine, and a Lite-On DVD
rewriter works on the nForce SATA just fine (ahci).
To muddy the waters further the LG drive on the nForce motherboard works
fine for reading. It'll even write a Blu-Ray disc happily*. It just
won't accept commands like "wodim -toc", "wodim <filename>", "growisofs
-Z" without Tejun's patch.
Luke
* I use the term loosely, it's a bit sulky about BD-R media.
--
``Doing linear scans over an associative array is like trying to club
someone to death with a loaded Uzi.'' -- Larry Wall
next prev parent reply other threads:[~2008-06-17 10:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 3:36 [PATCH #upstream-fixes 1/2] libata: don't check whether to use DMA or not for no data commands Tejun Heo
2008-06-17 3:37 ` [PATCH #upstream-fixes 2/2] libata: implement ATAPI_HORKAGE_NOPIO and apply it to GGW-H10N Tejun Heo
2008-06-17 8:43 ` Alan Cox
2008-06-17 9:14 ` Tejun Heo
2008-06-17 9:31 ` Tejun Heo
2008-06-17 9:54 ` Luke Ross [this message]
2008-06-17 10:04 ` Alan Cox
2008-06-17 12:27 ` Tejun Heo
2008-06-18 11:48 ` Luke Ross
2008-06-18 11:59 ` Jeff Garzik
2009-11-13 9:14 ` Dan Williams
2009-11-14 0:11 ` Robert Hancock
2009-11-15 8:16 ` Tejun Heo
2009-11-15 18:22 ` Robert Hancock
2009-11-18 2:14 ` Jeff Garzik
2009-11-24 16:50 ` Dan Williams
2009-11-15 11:13 ` Luke Ross
2008-06-17 8:54 ` Alan Cox
2008-06-19 0:28 ` [PATCH #upstream-fixes 1/2] libata: don't check whether to use DMA or not for no data commands Jeff Garzik
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=20080617095439.GA9359@lukeross.name \
--to=luke@lukeross.name \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).