Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\.11\s+4\/8\]\s+tg3\:\s+Add\s+msi\s+test\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[PATCH\s+2\.6\.11\s+4\/8\]\s+tg3\:\s+Add\s+msi\s+test\s*$/: 20 ]

Total 20 documents matching your query.

1. t (score: 1): Author: an@xxxxxxxxx>; Date: Sun, 20 Mar 2005 23:43:03 -0800; Add an MSI test to make sure MSI is working at the system level. If the test fails, the driver will go back to INTx mode. Signed-off-by: Michael Chan <mchan@xxxxxxxxxxxx> Attachment: tg3-4.patch Desc; /archives/netdev/2005-03/msg01165.html (8,573 bytes)
2. : [PATCH 2.6.11 3/8] tg3: Add msi support for 5750 C0 (score: 1): Author: rdson <mcr@xxxxxxxxxxxxxxxxxxxxxx>; Date: Tue, 22 Mar 2005 15:57:35 -0500; Michael Chan wrote: Add an MSI test to make sure MSI is working at the system level. If the test fails, the driver will go back to INTx mode. Signed-off-by: Michael Chan <mchan@xxxxxxxxxxxx In theory; /archives/netdev/2005-03/msg01227.html (9,119 bytes)
3. dummy as IMQ replacement (score: 1): Author: ff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 14:07:13 -0800; Some older chipsets/APICs in older PCI machines do not properly support MSI. In some cases you will get no interrupts and in a few cases you can get SERR/NMI because the MSI cycle terminates abnorma; /archives/netdev/2005-03/msg01234.html (9,469 bytes)
4. cket dumping (score: 1): Author: arzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 17:14:58 -0500; Michael Chan wrote: Some older chipsets/APICs in older PCI machines do not properly support MSI. In some cases you will get no interrupts and in a few cases you can get SERR/NMI because the MSI cycle; /archives/netdev/2005-03/msg01235.html (9,902 bytes)
5. Add msi test (score: 1): Author: arzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 14:17:14 -0800; Right. 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; /archives/netdev/2005-03/msg01236.html (9,172 bytes)
6. Add msi test (score: 1): Author: garzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 17:26:44 -0500; David S. Miller wrote: 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_ms; /archives/netdev/2005-03/msg01237.html (10,972 bytes)
7. Experimental Driver for Neterion/S2io 10GbE Adapters (score: 1): Author: <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 15:40:30 -0800; It actually spots them too. :-) If you'd like it to print out something like: TG3 MSI test failed on chipset ven[%x] devid[%x] please email this info to PCI maintainers at x@xxxxx that's fine. Just b; /archives/netdev/2005-03/msg01251.html (9,706 bytes)
8. (score: 1): Author: orth" <dale@xxxxxxxxxxxxxx>; Date: Tue, 22 Mar 2005 18:50:36 -0500; David S. Miller wrote: Just because it's what we've been doing doesn't mean it's the best solution in this case. If you hope users will just report this stuff, most of them won't. They'll say Linux d; /archives/netdev/2005-03/msg01253.html (10,200 bytes)
9. ster support (score: 1): Author: Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 15:52:35 -0800; When you come up with something that doesn't require the users to ask around and report stuff when MSI doesn't work, let me know. But for now let's hold off on the tg3 MSI support, ok?; /archives/netdev/2005-03/msg01254.html (9,267 bytes)
10. le_timeout() with msleep() (score: 1): Author: hadi@xxxxxxxxxx>; Date: Wed, 23 Mar 2005 10:16:23 -0800; Jeff, I understand your point of view which is from the kernel development perspective. For us, we have to consider the user's perspective when he is trying to figure out why things are not working.; /archives/netdev/2005-03/msg01321.html (9,381 bytes)
11. [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: "Michael Chan" <mchan@xxxxxxxxxxxx>; Date: Sun, 20 Mar 2005 23:43:03 -0800; Add an MSI test to make sure MSI is working at the system level. If the test fails, the driver will go back to INTx mode. Signed-off-by: Michael Chan <mchan@xxxxxxxxxxxx> Attachment: tg3-4.patch Desc; /archives/netdev/2005-03/msg03088.html (8,573 bytes)
12. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 15:57:35 -0500; Signed-off-by: Michael Chan <mchan@xxxxxxxxxxxx In theory, this patch is not necessary. pci_enable_msi() should fail, if MSI is not available at the system level. What behavior are you seeing? Jeff; /archives/netdev/2005-03/msg03150.html (9,075 bytes)
13. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: "Michael Chan" <mchan@xxxxxxxxxxxx>; Date: Tue, 22 Mar 2005 14:07:13 -0800; Some older chipsets/APICs in older PCI machines do not properly support MSI. In some cases you will get no interrupts and in a few cases you can get SERR/NMI because the MSI cycle terminates abnorma; /archives/netdev/2005-03/msg03157.html (9,469 bytes)
14. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 17:14:58 -0500; Michael Chan wrote: Some older chipsets/APICs in older PCI machines do not properly support MSI. In some cases you will get no interrupts and in a few cases you can get SERR/NMI because the MSI cycle; /archives/netdev/2005-03/msg03158.html (9,915 bytes)
15. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Tue, 22 Mar 2005 14:17:14 -0800; Right. 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; /archives/netdev/2005-03/msg03159.html (9,268 bytes)
16. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 17:26:44 -0500; 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 lo; /archives/netdev/2005-03/msg03160.html (10,904 bytes)
17. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Tue, 22 Mar 2005 15:40:30 -0800; It actually spots them too. :-) If you'd like it to print out something like: TG3 MSI test failed on chipset ven[%x] devid[%x] please email this info to PCI maintainers at x@xxxxx that's fine. Just b; /archives/netdev/2005-03/msg03174.html (9,863 bytes)
18. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: Jeff Garzik <jgarzik@xxxxxxxxx>; Date: Tue, 22 Mar 2005 18:50:36 -0500; If you hope users will just report this stuff, most of them won't. They'll say Linux doesn't work on my computer and I have real life stuff to take care of so I'll install freebsd or windows or a dif; /archives/netdev/2005-03/msg03176.html (10,418 bytes)
19. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxxxxx>; Date: Tue, 22 Mar 2005 15:52:35 -0800; When you come up with something that doesn't require the users to ask around and report stuff when MSI doesn't work, let me know. But for now let's hold off on the tg3 MSI support, ok?; /archives/netdev/2005-03/msg03177.html (9,485 bytes)
20. Re: [PATCH 2.6.11 4/8] tg3: Add msi test (score: 1): Author: "Michael Chan" <mchan@xxxxxxxxxxxx>; Date: Wed, 23 Mar 2005 10:16:23 -0800; Jeff, I understand your point of view which is from the kernel development perspective. For us, we have to consider the user's perspective when he is trying to figure out why things are not working.; /archives/netdev/2005-03/msg03244.html (9,381 bytes)

Current List: 1 - 20
Page: [1]