netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: andy@greyhouse.net, netdev@vger.kernel.org
Subject: Re: [TG3]: Workaround MSI bug on 5714/5780.
Date: Thu, 06 Sep 2007 12:50:19 -0700 (PDT)	[thread overview]
Message-ID: <20070906.125019.104036964.davem@davemloft.net> (raw)
In-Reply-To: <1189105530.4852.8.camel@dell>

From: "Michael Chan" <mchan@broadcom.com>
Date: Thu, 06 Sep 2007 12:05:30 -0700

> The HT1000 bridge may very well have an MSI issue.  I'm checking with
> ServerWorks and I will do some testing to confirm.  If confirmed, we can
> disable MSI behind the HT1000 bridge instead of globally.  The 5714
> issue is not caused by the HT1000 as it is not behind the HT1000.

What I'm going to do at this point is just merge the tg3
fix into the current 2.6.23 tree right now.

Meanwhile I'll have the HT1000 MSI quirk revert ready and,
unless we find a reason not to, I'll ask Greg KH to merge
that patch into 2.6.24

It seems the safest and most reasonable way to handle this
right now.

  parent reply	other threads:[~2007-09-06 19:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 20:07 [TG3]: Workaround MSI bug on 5714/5780 Michael Chan
2007-09-05 19:38 ` Andy Gospodarek
2007-09-06 11:02 ` David Miller
2007-09-06 13:45   ` Andy Gospodarek
2007-09-06 14:34     ` David Miller
2007-09-06 14:40       ` Andy Gospodarek
2007-09-06 15:41       ` Andy Gospodarek
2007-09-06 19:05         ` Michael Chan
2007-09-06 18:26           ` Andy Gospodarek
2007-09-06 19:50           ` David Miller [this message]
2007-09-06 20:27             ` Andy Gospodarek
2007-09-08  2:26             ` Michael Chan
2007-09-08 21:25               ` David Miller
2007-09-14 22:33               ` David Miller
2007-09-06 15:11     ` Michael Chan

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=20070906.125019.104036964.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andy@greyhouse.net \
    --cc=mchan@broadcom.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).