From: Petr Vandrovec <petr@vandrovec.name>
To: Roland Dreier <rdreier@cisco.com>
Cc: jeff@garzik.org, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Unbreak MSI on ATI devices
Date: Fri, 05 Jan 2007 01:07:01 -0800 [thread overview]
Message-ID: <459E1535.5020105@vandrovec.name> (raw)
In-Reply-To: <ada4pr61mie.fsf@cisco.com>
Roland Dreier wrote:
> > So my question is - what is real reason for disabling INTX when in MSI mode?
> > According to PCI spec it should not be needed, and it hurts at least chips
> > listed below:
> >
> > 00:13.0 0c03: 1002:4374 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
> > 00:13.1 0c03: 1002:4375 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller
> > 00:13.2 0c03: 1002:4373 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller
>
> heh... I'm not gloating or anything... but I am glad that some ASIC
> designer was careless enough to prove me right when I said going
> beyond what the PCI spec requires is dangerous.
Hi,
unfortunately it is not everything :-(
I cannot get MSI to work on IDE interface under any circumstances - in
legacy mode it always uses IRQ14/15 regardless of whether MSI is enabled
or not (that's probably correct), but in native mode as soon as I enable
MSI it either does not deliver interrupts at all (definitely not through
IRQ14/15, and, if I got routing right, also not through its INTA#), or
it delivers them somewhere else than where programmed. As my boot
device is connected to this adapter, and it is a notebook, it is not
easy to debug what's really going on :-(
00:14.1 0101: 1002:4376 IDE interface: ATI Technologies Inc Standard
Dual Channel PCI IDE Controller ATI (prog-if 8f [Master SecP SecO PriP
PriO])
Subsystem: Rioworks Unknown device 2043
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 18
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=4]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=4]
I/O ports at 8410 [size=16]
Capabilities: [70] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
Petr
next prev parent reply other threads:[~2007-01-05 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 7:55 [PATCH] Unbreak MSI on ATI devices Petr Vandrovec
2006-12-21 8:21 ` Jeff Garzik
2006-12-25 4:01 ` Daniel Barkalow
2007-01-04 21:59 ` Roland Dreier
2007-01-05 9:07 ` Petr Vandrovec [this message]
2007-01-06 0:54 ` Daniel Barkalow
2007-01-05 23:57 ` Daniel Barkalow
[not found] <fa.yZrxrHh1AWLcv/+D2xYZ1VhVYb8@ifi.uio.no>
2006-12-21 14:36 ` Robert Hancock
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=459E1535.5020105@vandrovec.name \
--to=petr@vandrovec.name \
--cc=akpm@osdl.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.