From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: gshan <gshan@alcatel-lucent.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: PIIX4: DMA timeout issue
Date: Wed, 30 Jul 2008 11:49:34 +0100 [thread overview]
Message-ID: <20080730114934.5a593cf4@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <48902EB5.8070102@alcatel-lucent.com>
> Jeff, I tried moving to ATA driver for PIIX4 today and found ATA need to
> request
> 2 IRQ lines, each one of them belongs to primary and secondary channel.
> However,
> when I make PIIX4 worked under IDE driver, it also need to request one
> IRQ for "ide1".
> So it's necessary to disable secondary channel manually?
If the controller is in legacy mode then libata will claim the interrupt
lines for all channels which are enabled even if there are no devices on
them. This is neccessary for device hot or warm plug support as new disks
could appear on empty channels.
>
> Another question is my PIIX4 chip has device ID + vendor ID of
> 0x71108086. But it finally
> was mapped to following ID of piix_pci_tbl[] array. Device of 0x7110 and
> 0x7010 should
> be quit different, right?
Yes - I find tht one very odd - you might need to debug a bit to see what
is occuring if you think this is the case.
Alan
next prev parent reply other threads:[~2008-07-30 11:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 8:43 gshan
2008-07-29 13:34 ` Jeff Garzik
[not found] ` <200807291713.29580.bzolnier@gmail.com>
2008-07-30 0:57 ` gshan
2008-07-30 19:43 ` Bartlomiej Zolnierkiewicz
2008-07-31 1:00 ` gshan
2008-07-30 0:58 ` gshan
2008-07-30 9:04 ` gshan
2008-07-30 10:49 ` Alan Cox [this message]
2008-07-31 4:30 ` gshan
2008-08-01 7:43 ` Tejun Heo
2008-08-01 8:38 ` gshan
2008-08-01 8:54 ` gshan
2008-08-03 14:10 ` Gavin Shan
2008-08-05 3:41 ` gshan
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=20080730114934.5a593cf4@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gshan@alcatel-lucent.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--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
all inboxes | Powered by JetHome®