From: Jeff Garzik <jeff@garzik.org>
To: David Miller <davem@davemloft.net>
Cc: mchan@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH][BNX2]: Disable MSI on 5706 if AMD 8132 bridge is present
Date: Fri, 29 Sep 2006 20:38:07 -0400 [thread overview]
Message-ID: <451DBC6F.2010901@garzik.org> (raw)
In-Reply-To: <20060929.162958.102576741.davem@davemloft.net>
David Miller wrote:
> From: Jeff Garzik <jeff@garzik.org>
> Date: Fri, 29 Sep 2006 19:15:14 -0400
>
>> It was completely vague as to why this incompatibility was specific to
>> the 5706, when -- as the description noted -- the behavior is legal.
>>
>> Re-read the patch. At no time does it say 5706 was in the wrong.
>
> True, but it does indicate that using a masked 64-bit transaction
> for MSI instead of a true 32-bit one is considered to be quite rare.
>
> Do you wish to put a table of all devices that do this, and at PCI
> quirk time disable PCI for everyone on the AMD chipset if even one
> such device is found in the device?
>
> That doesn't make any sense to me.
David, rejoin reality. You are either arguing with a fictionalized Jeff
Garzik in your head, or constructing a classical strawman.
Let me say it for the cheap seats: AT NO TIME DID I PROPOSE ACTION OF
ANY KIND. I sought clarification. Information.
So, please, quit making stupid and incorrect assumptions about my
intentions. If this is indeed a rare behavior and most other MSI cases
work with the 8132, then the patch is quite reasonable. I see no reason
to NAK the patch.
Jeff
next prev parent reply other threads:[~2006-09-30 0:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 21:07 [PATCH][BNX2]: Disable MSI on 5706 if AMD 8132 bridge is present Michael Chan
2006-09-29 21:28 ` Jeff Garzik
2006-09-29 21:39 ` Michael Chan
2006-09-29 22:49 ` David Miller
2006-09-29 23:00 ` Jeff Garzik
2006-09-29 23:08 ` David Miller
2006-09-29 23:15 ` Jeff Garzik
2006-09-29 23:27 ` Michael Chan
2006-09-29 23:29 ` David Miller
2006-09-30 0:38 ` Jeff Garzik [this message]
2006-09-30 1:22 ` David Miller
2006-09-29 23:46 ` Rick Jones
2006-09-30 0:16 ` Roland Dreier
2006-09-30 0:07 ` David Miller
2006-09-30 10:13 ` Brice Goglin
2006-09-30 18:09 ` 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=451DBC6F.2010901@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.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).