On Tue, Jun 07, 2005 at 10:08:20PM +0200, Francois Romieu wrote:-
-> it does not match your 0006 revision. No wonder nothing gets detected.
As a quick hack, one could cross fingers and add a
CH_DEVICE(6, 0, CH_BRD_N110_1F)
or, if it does not work:
CH_DEVICE(6, 1, CH_BRD_N210_1F)
I added:
enum {
CH_BRD_T110_1F,
CH_BRD_N110_1F,
CH_BRD_N210_1F,
CH_BRD_T210_1F,
};
struct pci_device_id t1_pci_tbl[] = {
CH_DEVICE(6, 0, CH_BRD_T110_1F),
CH_DEVICE(6, 1, CH_BRD_T110_1F),
CH_DEVICE(7, 0, CH_BRD_N110_1F),
CH_DEVICE(10, 1, CH_BRD_N210_1F),
{ 0, }
};
according to 2.6.6 driver.
However, it seems to be highly unstable. Using iperf it gets broken. Card receives packets but it does not transmit after some iperf tests.
Using tcpdump I see things like this:
tcpdump -ni eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
23:05:03.854587 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 1
23:05:04.853853 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 2
23:05:05.853965 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 3
23:05:06.854079 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 4
23:05:07.854193 IP 10.0.0.1 > 10.0.0.2: icmp 64: echo request seq 5
If it does not work at all, someone will have to dissect the whole
thing. Please fill an entry at bugzilla.kernel.org, add it your lspci info
and make it link the 2.6.6 driver from Chelsio's website.
Should I still add an bugzilla entry? Unfortunately, 2.6.6. driver from website
is accessible only through password.