From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Mike Marciniszyn
<mike.marciniszyn-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>
Cc: roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] IB/qib: detour pcie_caps for certain chip sets
Date: Wed, 11 Jan 2012 22:48:30 -0700 [thread overview]
Message-ID: <20120112054830.GB32082@obsidianresearch.com> (raw)
In-Reply-To: <20120112030049.31831.62692.stgit-hIFRcJ1SNwcXGO8/Qfapyjg/wwJxntczYPYVAmT7z5s@public.gmane.org>
On Wed, Jan 11, 2012 at 10:00:49PM -0500, Mike Marciniszyn wrote:
> Commit 8d4548f2b ("IB/qib: Default some module parameters optimally")
> introduced an issue with older root complexes. They cannot handle
> the pcie_caps of 0x51.
Should whatever this issue is be a general PCI fixup? Like broken MSI,
etc.
Might be nice to include what 0x51 tunes in the commit to aide other
peoole with the broken chipset :)
Isn't it necesary to check the PCI vendor as well as the devid?
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-12 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 3:00 [PATCH] IB/qib: detour pcie_caps for certain chip sets Mike Marciniszyn
[not found] ` <20120112030049.31831.62692.stgit-hIFRcJ1SNwcXGO8/Qfapyjg/wwJxntczYPYVAmT7z5s@public.gmane.org>
2012-01-12 5:48 ` Jason Gunthorpe [this message]
[not found] ` <20120112054830.GB32082-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-01-12 7:06 ` Roland Dreier
2012-01-12 16:02 ` Mike Marciniszyn
[not found] ` <35AAF1E4A771E142979F27B51793A4888885A5E388-HolNjIBXvBOXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2012-01-12 20:27 ` Jason Gunthorpe
2012-01-12 7:06 ` Roland Dreier
[not found] ` <CAL1RGDXOO6baaET_fCFT3YUsK9aqGkODoHnd1FNwOp_szZO4Gw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-12 17:17 ` Mike Marciniszyn
[not found] ` <35AAF1E4A771E142979F27B51793A4888885A5E3AE-HolNjIBXvBOXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2012-01-12 21:57 ` Roland Dreier
[not found] ` <CAL1RGDW2DcU_kp46BfRJjQjkEYxcCqRzqdgOC-AAhUsXsDb8gQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-01-12 22:14 ` Mike Marciniszyn
[not found] ` <35AAF1E4A771E142979F27B51793A4888885A5E45C-HolNjIBXvBOXx9kJd3VG2h2eb7JE58TQ@public.gmane.org>
2012-01-12 22:23 ` Jason Gunthorpe
[not found] ` <20120112222328.GI31021-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2012-01-12 22:35 ` Mike Marciniszyn
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=20120112054830.GB32082@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mike.marciniszyn-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@public.gmane.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