Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

3com 3c996b-t support?

1 view
Skip to first unread message

Jes Sorensen

unread,
Jul 24, 2002, 1:42:11 PM7/24/02
to
>>>>> "Steve" == kwijibo <kwi...@zianet.com> writes:

Steve> http://www.cs.uni.edu/~gray/gig-over-copper/

Steve> The 3com drivers are open-source though, which makes me less
Steve> hesitent. And the tigon3 drivers lack of documentation kind of
Steve> irks me. I would however like to stick with a mainstream
Steve> kernel driver cause the support is there if it is needed. I
Steve> guess I will give both versions a whirl. From just glancing at
Steve> the source of both, it seems that both versions support jumbo
Steve> frames which is really what I am after.

Well did you look at the code? It's the infamous Broadcom bcm5700
driver which is probably the worst driver code we have seen in the
Linux community for the last 5 years. Sure you can run it, but don't
come back and complain when you run into trouble. You will be a lot
better off using the tg3 driver, or better yet, getting a NIC thats
less buggy.

Cheers,
Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Jes Sorensen

unread,
Jul 24, 2002, 2:08:25 PM7/24/02
to
>>>>> "Steve" == kwijibo <kwi...@zianet.com> writes:

Steve> Jes Sorensen wrote:

>> driver which is probably the worst driver code we have seen in the
>> Linux community for the last 5 years. Sure you can run it, but
>> don't come back and complain when you run into trouble. You will be
>> a lot better off using the tg3 driver, or better yet, getting a NIC
>> thats less buggy.

Steve> Is the NIC hardware buggy or is it just the bcm5700 drivers?

The hardware is buggy. The bcm5700 drivers are written in such
terrible C, you can in fact argue whether you'd call it C, that it's
totally impossible to debug the code anyway. Who knows whats hidden in
there.

kwi...@zianet.com

unread,
Jul 24, 2002, 2:09:54 PM7/24/02
to

Jes Sorensen wrote:

>>>>>>"Steve" == kwijibo <kwi...@zianet.com> writes:
>>>>>>
>>>>>>
>

>Steve> http://www.cs.uni.edu/~gray/gig-over-copper/
>
>Steve> The 3com drivers are open-source though, which makes me less
>Steve> hesitent. And the tigon3 drivers lack of documentation kind of
>Steve> irks me. I would however like to stick with a mainstream
>Steve> kernel driver cause the support is there if it is needed. I
>Steve> guess I will give both versions a whirl. From just glancing at
>Steve> the source of both, it seems that both versions support jumbo
>Steve> frames which is really what I am after.
>
>Well did you look at the code? It's the infamous Broadcom bcm5700
>

Just glanced at it.

>driver which is probably the worst driver code we have seen in the
>Linux community for the last 5 years. Sure you can run it, but don't
>come back and complain when you run into trouble. You will be a lot
>better off using the tg3 driver, or better yet, getting a NIC thats
>less buggy.
>
>

Is the NIC hardware buggy or is it just the bcm5700 drivers?

Well that answers the question I was after, I will use the
tg3 kernel drivers. I chose this card cause it had good
performance tests on that web page. The SK9821 beat
all the gigi NICs but it also costs about 4 times as much
as any other.

Steve

0 new messages