| To: | Jeff Garzik <jgarzik@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2.6.11 4/8] tg3: Add msi test |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Tue, 22 Mar 2005 14:17:14 -0800 |
| Cc: | mchan@xxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <424098E2.6090007@pobox.com> |
| References: | <B1508D50A0692F42B217C22C02D84972020F3E2E@NT-IRVA-0741.brcm.ad.broadcom.com> <424098E2.6090007@pobox.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Tue, 22 Mar 2005 17:14:58 -0500 Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > OK, so this is not a tg3-related problem at all. Right. > It really sounds like you should update pci_msi_quirk() to cover the > other affected cases. That's not possible without either: 1) getting a lot of chipset vendors to reveal stuff they probably would rather keep secret (ie. that their chip in particular has MSI problems) 2) having a device on which to perform the MSI usability check See #2? That's the main issue from genericizing this, we need a device on which to perform the usability check so that we can handling a test interrupt and see if state got updated correctly. So for the time being, Michael's change is OK until we find a better solution that really does cover all the problem chipsets. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2.6.11 4/8] tg3: Add msi test, Jeff Garzik |
|---|---|
| Next by Date: | Re: [PATCH 2.6.11 4/8] tg3: Add msi test, Jeff Garzik |
| Previous by Thread: | Re: [PATCH 2.6.11 4/8] tg3: Add msi test, Jeff Garzik |
| Next by Thread: | Re: [PATCH 2.6.11 4/8] tg3: Add msi test, Jeff Garzik |
| Indexes: | [Date] [Thread] [Top] [All Lists] |