From: Jens Axboe <axboe@suse.de>
To: Andi Kleen <ak@suse.de>
Cc: jgarzik@pobox.com, B.Zolnierkiewicz@elka.pw.edu.pl,
linux-ide@vger.kernel.org, jun.nakajima@intel.com
Subject: Re: PATA handling on ICH5R in 2.6.8rc2
Date: Wed, 4 Aug 2004 19:26:10 +0200 [thread overview]
Message-ID: <20040804172610.GA5978@suse.de> (raw)
In-Reply-To: <20040804184504.21dcb386.ak@suse.de>
On Wed, Aug 04 2004, Andi Kleen wrote:
>
> Hallo,
>
> I have a machine with a ICH5R southbridge and a PATA DVD hanging off
> it. When I compile the kernel without CONFIG_BLK_DEV_IDE_SATA then
> the old IDE driver detects the DVD anyways, but refuses to enable DMA
> (because the PCI ID entry is not compiled into piix.c). It doesn't
> even disable -u1 which causes quite some problems when accessing the
> CD ROM: I get endless floods of "too many lost ticks", which means it
> has spent more than 100 jiffies with interrupts off doing something. I
> fixed this with hdparm -u1, but it's still quite slow with DMA off.
>
> I could enable BLK_DEV_IDE_SATA, but then the old IDE driver would try
> to drive all SATA drives, which would be wrong I guess.
>
> I presume the right way to fix it would be to always readd the PCI ID
> entry for 82801EB_1 to piix.c, but only let it be handled by the old
> driver when there is a PATA DVD on the controller (and leave the other
> controllers to libata). Still this could get conflicts when there is a
> real SATA device on the same controller (can this happen?)
>
> For that the piix.c probe function would just need to do a quick cable
> check and ignore the device when it is SATA and when BLK_DEV_IDE_SATA
> is unset. I looked through the Intel ICH5 manuals, but it was not
> obvious to me how to probe this non intrusively. I suppose one way
> would be to go through the full IDE driver initialization for the
> drive, and then when SATA is detected bail out again and reset the
> controller and leave it for libata.
>
> Or drive the DVD always with libata? Does it have an working ATAPI
> driver yet?
>
> Is there a better solution for this problem?
Can't you set it to enhanced mode in the bios, then shows up as a
seperate device id and just works. I had the same issue until Jeff
walked me through it :-)
--
Jens Axboe
next prev parent reply other threads:[~2004-08-04 17:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 16:45 PATA handling on ICH5R in 2.6.8rc2 Andi Kleen
2004-08-04 17:26 ` Jens Axboe [this message]
2004-08-04 17:36 ` Andi Kleen
2004-08-04 19:20 ` 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=20040804172610.GA5978@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=ak@suse.de \
--cc=jgarzik@pobox.com \
--cc=jun.nakajima@intel.com \
--cc=linux-ide@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