From: Tejun Heo <htejun@gmail.com>
To: Shane Huang <Shane.Huang@amd.com>
Cc: David Miller <davem@davemloft.net>,
david.gaarenstroom@gmail.com, linux-kernel@vger.kernel.org,
jeff@garzik.org, barkalow@iabervon.org, linas@austin.ibm.com,
gregkh@suse.de, brice.goglin@gmail.com,
linux-pci@atrey.karlin.mff.cuni.cz, linux-ide@vger.kernel.org,
brice@myri.com, mchan@broadcom.com
Subject: Re: [PATCH 5/5]: [PCI]: Remove 3 incorrect MSI quirks.
Date: Mon, 29 Oct 2007 15:13:48 +0900 [thread overview]
Message-ID: <47257A1C.8050206@gmail.com> (raw)
In-Reply-To: <5CAB7B5D6F8AB84AA868A46B47A50705623160@sshaexmb1.amd.com>
Shane Huang wrote:
>> I would like those to be removed, but to be conservative we should
>> first get some testing feedback that confirms this just like those
>> provided to me from the AMD folks for the RS690, RX790 and RD580
>> cases.
>>
>> Otherwise the risk to break people's systems is very real.
>
> In fact, our team only has boards with RS690+SB700 and RX790+SB700,
> I don't know why the RD580 MSI is disabled too by the patch
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commi
> t;h=aea6a433f50cd89b9cbd10850fd0b32f961f9883
> Maybe Tejun can give us more information on this case,
> I think the cause should be same as RS690 and RX790.
I don't remember history of each quirk entry but they're either reported
in a bug report and successfully worked around with pci=nomsi or one of
AMD guys told me certain PCI IDs share the same problem. I can dig mail
archive if you wanna know how it went down for RD580.
--
tejun
prev parent reply other threads:[~2007-10-29 6:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 8:17 [PATCH 5/5]: [PCI]: Remove 3 incorrect MSI quirks David Miller
2007-10-26 10:56 ` David Gaarenstroom
2007-10-26 11:38 ` David Miller
2007-10-28 20:11 ` David Gaarenstroom
2007-10-29 1:08 ` David Miller
2007-10-29 6:06 ` Shane Huang
2007-10-29 6:13 ` Tejun Heo [this message]
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=47257A1C.8050206@gmail.com \
--to=htejun@gmail.com \
--cc=Shane.Huang@amd.com \
--cc=barkalow@iabervon.org \
--cc=brice.goglin@gmail.com \
--cc=brice@myri.com \
--cc=davem@davemloft.net \
--cc=david.gaarenstroom@gmail.com \
--cc=gregkh@suse.de \
--cc=jeff@garzik.org \
--cc=linas@austin.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mchan@broadcom.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;
as well as URLs for NNTP newsgroup(s).