Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Andreas Seltenreich <s_selten@informatik.uni-karlsruhe.de>
To: "B. Douglas Hilton" <bdhilton@charter.net>
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 00:37:15 +0200	[thread overview]
Message-ID: <20020817223713.GA25852@gate450.dyndns.org> (raw)
In-Reply-To: <3D5EB2D6.9090403@charter.net>

[-- Attachment #1: Type: text/plain, Size: 909 bytes --]

Hi,

just append " || defined(__hppa__)" to line 47 of drivers/net/eepro100.c
I got mine working that way.

Regards,
andreas

* B. Douglas Hilton <bdhilton@charter.net> [2002-08-17 22:32]:
> Hello list. For some reason my onboard LAN devices
> all mysteriously died and disappeared from the
> firmware, so I purchased an eepro100 card to try
> and get some networking connectivity back.
> 
> When I modprobe eepro100 it seems to be ok. I can
> do an 'ifup -a' and then ifconfig lists my eth0
> and it appears to be configured properly. I can
> ping other servers in my LAN, and I can do an
> ftp login, but as soon a I type "ls" it goes out
> to lunch and locks up.
> 
> Likewise I can ping numeric ip's on the internet,
> but name resolution is not working.
> 
> Could this be an endianness problem? Any ideas?
> 
> Any tips on how to reactivate the onboard ether
> devices would be greatly appreciated too.

[-- Attachment #2: diff --]
[-- Type: text/plain, Size: 465 bytes --]

--- linux/drivers/net/eepro100.c	Mon Aug  5 02:12:20 2002
+++ linux/drivers/net/eepro100.c	Sun Aug 18 00:15:55 2002
@@ -44,7 +44,7 @@
 /* Set the copy breakpoint for the copy-only-tiny-buffer Rx method.
    Lower values use more memory, but are faster. */
 #if defined(__alpha__) || defined(__sparc__) || defined(__mips__) || \
-    defined(__arm__)
+    defined(__arm__) || defined(__hppa__)
 static int rx_copybreak = 1518;
 #else
 static int rx_copybreak = 200;

  reply	other threads:[~2002-08-17 22:37 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 [this message]
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
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=20020817223713.GA25852@gate450.dyndns.org \
    --to=s_selten@informatik.uni-karlsruhe.de \
    --cc=bdhilton@charter.net \
    --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