From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.6.12-rc6-mm1 & Chelsio driver
Date: Tue, 7 Jun 2005 23:10:48 +0200 [thread overview]
Message-ID: <20050607211048.GO2369@mail.muni.cz> (raw)
In-Reply-To: <20050607200820.GA25546@electric-eye.fr.zoreil.com>
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.
--
Lukáš Hejtmánek
next prev parent reply other threads:[~2005-06-07 21:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 18:13 Kernel 2.6.12-rc6-mm1 & Chelsio driver Lukas Hejtmanek
2005-06-07 18:50 ` Jeff Garzik
2005-06-07 18:58 ` Lukas Hejtmanek
2005-06-07 19:27 ` Jeff Garzik
2005-06-07 19:33 ` Lukas Hejtmanek
2005-06-07 20:08 ` Francois Romieu
2005-06-07 21:10 ` Lukas Hejtmanek [this message]
2005-06-07 22:42 ` Francois Romieu
2005-06-08 2:19 ` Scott Bardone
2005-06-08 6:50 ` Lukas Hejtmanek
2005-06-08 17:46 ` Christoph Hellwig
2005-06-08 18:43 ` Scott Bardone
2005-06-08 17:33 Scott Bardone
2005-06-08 18:49 ` Lukas Hejtmanek
2005-06-08 19:11 ` Scott Bardone
2005-06-08 19:32 ` Lukas Hejtmanek
2005-06-08 20:06 ` Scott Bardone
[not found] ` <42A74F88.10502@chelsio.com>
2005-06-16 23:22 ` Lukas Hejtmanek
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=20050607211048.GO2369@mail.muni.cz \
--to=xhejtman@mail.muni.cz \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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).