From: "B. Douglas Hilton" <bdhilton@charter.net>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: parisc-linux@lists.parisc-linux.org, saw@saw.sw.com.sg
Subject: Re: [parisc-linux] PCI Intel EtherExpressPro100 strangeness on C200 machine.
Date: Sun, 18 Aug 2002 11:55:11 -0400 [thread overview]
Message-ID: <3D5FC35F.7060402@charter.net> (raw)
In-Reply-To: 20020818051633.209BD4829@dsl2.external.hp.com
Here is my dmesg output that your requested, and my
ifconfig status right after booting. I typed this in
by hand, hopefully no typos.
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
eth0: Intel Corp. 82557 [Ethernet Pro 100], 00:90:27:60:CB:E6, IRQ 130.
Board assembly 721383-006, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0x8b51f404).
eth0 Link encap:Ethernet HWaddr:00:90:27:60:CB:E6
inet addr:192.168.100.115 Bcast:192.168.100.255 Mask:255.255.255.0
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2668 (2.6 KiB) TX bytes:558 (558.0 b)
Interrupt:130 Base address:0xf000
Well, I'm heading out to camp. Back on Monday.
Cheers!
- Doug
Grant Grundler wrote:
> Andreas Seltenreich wrote:
>
>>just append " || defined(__hppa__)" to line 47 of drivers/net/eepro100.c
>>I got mine working that way.
>
>
> The RX_ALIGN shouldn't strictly be needed. It's a performance improvement.
> It means the misaligned access handling isn't working right. And should be
> spewing something to the kernel dmesg buf. IIRC, Randolph Chung has done a
> great job on getting most of the misaligned access emulation working right.
> If you get console/dmesg output when using eepro100, please post it here.
>
> If someone with CVS access has time, please enable the RX_ALIGN
> code for __hppa__ as well. I have other changes outstanding (cpqfc)
> that I want to finished up and committed first.
>
> grant
>
next prev parent reply other threads:[~2002-08-18 15:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-17 20:32 [parisc-linux] PCI Intel EtherExpressPro100 strangeness on C200 machine B. Douglas Hilton
2002-08-17 22:37 ` Andreas Seltenreich
2002-08-18 2:01 ` B. Douglas Hilton
2002-08-18 3:12 ` Andreas Seltenreich
2002-08-18 3:33 ` B. Douglas Hilton
2002-08-18 5:16 ` Grant Grundler
2002-08-18 15:55 ` B. Douglas Hilton [this message]
2002-08-19 23:00 ` B. Douglas Hilton
2002-08-19 23:58 ` Grant Grundler
2002-08-20 0:04 ` Michael S.Zick
2002-08-20 0:18 ` Matt Taggart
2002-08-20 1:51 ` B. Douglas Hilton
2002-08-20 2:28 ` B. Douglas Hilton
2002-08-20 0:18 ` Grant Grundler
2002-08-20 8:23 ` Harri Haataja
2002-08-20 12:58 ` Andreas Seltenreich
2002-08-26 18:14 ` Grant Grundler
2002-08-30 6:37 ` Grant Grundler
2002-09-07 0:58 ` [parisc-linux] Opinions on desktop environments Derek Engelhaupt
2002-09-07 1:43 ` Alan Cox
2002-09-07 2:29 ` alaskan
2002-09-07 4:33 ` B. Douglas Hilton
2002-09-07 5:22 ` Derek Engelhaupt
2002-09-07 4:33 ` B. Douglas Hilton
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=3D5FC35F.7060402@charter.net \
--to=bdhilton@charter.net \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=saw@saw.sw.com.sg \
/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