From: Joel Soete <soete.joel@tiscali.be>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: parisc-linux <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] C110 builtin nic slow?
Date: Sat, 15 Nov 2003 19:41:27 +0000 [thread overview]
Message-ID: <3FB68167.10106@tiscali.be> (raw)
In-Reply-To: <20031112032230.GB12000@colo.lackof.org>
Hi Grant,
I quiet sure now that the pb come from the 2d nic of my pc.
It is a:
00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone]
(rev 24)
I with google, I find back a mail of Andrew Morton in which he mentioned
a diag tool for this nic (<http://www.scyld.com/diag/>). I launch it:
# ./vortex-diag -aem
[...]
Transceiver type in use: 10baseT.
MAC settings: full-duplex.
^^^^^^^^^^^^
Station address set to 00:10:4b:63:2e:bf.
Configuration options 000a.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
3Com Node Address 00:10:4B:63:2E:BF (used as a unique ID only).
OEM Station address 00:10:4B:63:2E:BF (used as the ethernet address).
Device ID 9055, Manufacturer ID 6d50.
Manufacture date (MM/DD/YYYY) 3/17/1998, division 6, product NK.
No BIOS ROM is present.
Transceiver selection: 10baseT.
Options: force full duplex, link beat required.
^^^^^^^^^^^^^^^^^
PCI Subsystem IDs: Vendor 10b7 Device 9055.
[...]
So i will continue to see how to set it up in half-duplex (would it not
be the default in 10BT?)
Cheers,
Joel
Grant Grundler wrote:
> On Tue, Nov 11, 2003 at 12:54:25PM +0000, Joel Soete wrote:
> ...
>
>>but on c110 I noticed many (with rx_copybreak = 100 and rx_copybreak =
>>1518):
>>do_page_fault() pid=882 command='netserver' type=15 address=0x0000001c
>>...
>
>
> hrm...this sounds familiar...I might have only run the netperf "client"
> on parisc and ran "netserver" on either ia64 or ia32 box. :^/
>
> sorry,
> grant
>
next prev parent reply other threads:[~2003-11-15 19:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 11:10 [parisc-linux] C110 builtin nic slow? Joel Soete
2003-11-10 12:31 ` Joel Soete
2003-11-10 14:00 ` Joel Soete
2003-11-10 17:35 ` Grant Grundler
2003-11-11 12:54 ` Joel Soete
2003-11-12 3:22 ` Grant Grundler
2003-11-15 19:41 ` Joel Soete [this message]
2003-11-15 22:56 ` M. Grabert
2003-11-15 23:22 ` [parisc-linux] Dual NICs on 9000/715, anyone? buggz
2003-11-15 23:34 ` Matthew Wilcox
2003-11-15 23:50 ` buggz
2003-11-16 1:51 ` Grant Grundler
2003-11-16 4:16 ` Shane G. Brodie
2003-11-16 4:32 ` Grant Grundler
2003-11-15 23:58 ` [parisc-linux] C110 builtin nic slow? M. Grabert
2003-11-16 17:00 ` Joel Soete
2003-11-21 21:44 ` Joel Soete
2003-11-21 22:37 ` Joel Soete
2003-11-16 16:53 ` Joel Soete
2003-11-10 17:37 ` Grant Grundler
2003-11-10 19:23 ` Joel Soete
2003-11-10 20:38 ` Joel Soete
2003-11-11 1:31 ` M. Grabert
2003-11-11 11:45 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2003-10-26 16:49 Joel Soete
2003-10-26 17:25 ` Grant Grundler
2003-10-26 20:40 ` Joel Soete
2003-10-26 21:10 ` Joel Soete
2003-10-27 19:39 ` Grant Grundler
2003-10-27 20:13 ` Matthew Wilcox
2003-10-28 8:39 ` Joel Soete
2003-10-28 19:32 ` Joel Soete
2003-10-28 19:34 ` Matthew Wilcox
2003-10-29 6:43 ` Joel Soete
2003-11-10 4:36 ` Grant Grundler
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=3FB68167.10106@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
/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