From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Dean Hildebrand <seattleplus@gmail.com>
Cc: linux-kernel@vger.kernel.org, dada1@cosmosbay.com
Subject: Re: PCI: Limit VPD length for Broadcom 5708S
Date: Thu, 7 Aug 2008 08:56:34 -0700 [thread overview]
Message-ID: <200808070856.34679.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <4898A0B2.3070201@gmail.com>
On Tuesday, August 5, 2008 11:49 am Dean Hildebrand wrote:
> > I have no idea if 5706S and 5709S also needs this truncation ofVPDlength
>
> It seems that our IBM Blade servers using 5706S also require this
> fix. We have confirmed that the patch below works on 2.6.27-rc1.
>
>
> diff -uprN linux-2.6.27-rc1/drivers/pci/quirks.c
> linux-2.6.27-rc1-fix/drivers/pci/quirks.c
> --- linux-2.6.27-rc1/drivers/pci/quirks.c 2008-08-05
> 10:51:42.000000000 -0700
> +++ linux-2.6.27-rc1-fix/drivers/pci/quirks.c 2008-08-05
> 10:50:57.000000000 -0700
> @@ -1756,9 +1756,10 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_VI
> */
> static void __devinit quirk_brcm_570x_limit_vpd(struct pci_dev *dev)
> {
> - /* Only disable the VPD capability for 5706, 5708, and 5709
> rev. A */
> + /* Only disable the VPD capability for 5706, 5706S, 5708, and
> 5709 rev. A */
> if ((dev->device == PCI_DEVICE_ID_NX2_5706) ||
> (dev->device == PCI_DEVICE_ID_NX2_5708) ||
> + (dev->device == PCI_DEVICE_ID_NX2_5706S) ||
> ((dev->device == PCI_DEVICE_ID_NX2_5709) &&
> (dev->revision & 0xf0) == 0x0)) {
> if (dev->vpd)
Looks fine. Can you respin against my for-linus branch and resubmit with a
signed-off-by and full changelog?
Thanks,
Jesse
next prev parent reply other threads:[~2008-08-07 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aVL4E-5C9-7@gated-at.bofh.it>
[not found] ` <2d9716d7-99a4-4d17-9cae-83842e216c8c@y19g2000prn.googlegroups.com>
2008-08-05 18:49 ` PCI: Limit VPD length for Broadcom 5708S Dean Hildebrand
2008-08-07 15:56 ` Jesse Barnes [this message]
2008-08-08 0:31 ` Dean Hildebrand
2008-08-08 0:50 ` Jesse Barnes
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=200808070856.34679.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seattleplus@gmail.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