public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Danny ter Haar <dth@lin-gen.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Hans Grobler <grobh@sun.ac.za>, linux-kernel@vger.kernel.org
Subject: Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4
Date: Mon, 15 Jan 2001 17:29:07 +0100	[thread overview]
Message-ID: <20010115172907.A1708@lin-gen.com> (raw)
In-Reply-To: <93kn8a$itt$1@voyager.cistron.net> <Pine.LNX.4.30.0101111836460.30013-100000@prime.sun.ac.za> <20010112125010.A6371@lin-gen.com> <20010112233332.C2501@alpha.franken.de>
In-Reply-To: <20010112233332.C2501@alpha.franken.de>; from tsbogend@alpha.franken.de on Fri, Jan 12, 2001 at 11:33:32PM +0100

I experimented some further today.

using some printk i found out is was setting Fullduplex,
hardcoded that to half-duplex (mine is connected to a hub
and not a switch) , and it's configuration was 100Mbit
as it was supposed to.

Then i started looking at the start_xmit code and got
lost :-)))

Hope this helpes to pin-point the problem.

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

  reply	other threads:[~2001-01-15 16:29 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09  9:12 Failure building 2.4 while running 2.4. Success in building 2.4 while running 2.2 Silviu Marin-Caea
2001-01-09 10:17 ` Alessandro Suardi
2001-01-09 10:33   ` Failure building 2.4 while running 2.4. Success in building 2.4 Alan Cox
2001-01-09 18:20     ` Failure building 2.4 while running 2.4. There is no such thing Silviu Marin-Caea
2001-01-09 18:43       ` Alan Cox
2001-01-09 19:57       ` Drivers under 2.4 Dennis
2001-01-09 20:13         ` suser checks in 2.2.x Bosko Radivojevic
2001-01-09 18:39           ` Arnaldo Carvalho de Melo
2001-01-10 18:22       ` Drivers under 2.4 Dennis
2001-01-10 20:01         ` Hans Grobler
2001-01-10 21:37         ` Dennis
2001-01-10 21:38           ` Andi Kleen
2001-01-10 22:08             ` Hans Grobler
2001-01-11 10:24               ` Danny ter Haar
2001-01-11 10:31                 ` Andi Kleen
2001-01-11 10:58                   ` Danny ter Haar
2001-01-11 11:36                     ` Andrew Morton
2001-01-11 11:58                       ` Danny ter Haar
2001-01-11 14:00                         ` Danny ter Haar
2001-01-11 14:32                           ` Jeff Garzik
2001-01-11 16:33                             ` Danny ter Haar
2001-01-11 16:44                               ` Hans Grobler
2001-01-12 11:50                                 ` PRoblem with pcnet32 under 2.4.0 , was :Drivers " Danny ter Haar
2001-01-12 12:01                                   ` Hans Grobler
2001-01-12 12:16                                     ` Danny ter Haar
2001-01-12 22:33                                   ` Thomas Bogendoerfer
2001-01-15 16:29                                     ` Danny ter Haar [this message]
2001-01-11 12:56                 ` Drivers " Alan Cox
2001-01-09 10:28 ` Failure building 2.4 while running 2.4. Success in building 2.4 while running 2.2 Alan Cox
2001-01-09 16:10 ` [rlug] " Eugen
2001-01-09 19:01 ` J Sloan

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=20010115172907.A1708@lin-gen.com \
    --to=dth@lin-gen.com \
    --cc=grobh@sun.ac.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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