From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Grant Erickson <grant@lcse.umn.edu>
Cc: Niklaus Giger <n.giger@netstal.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Help Sought: 8390-Ethernet Troubles on PowerPC 4xx Port
Date: Mon, 17 Jan 2000 06:04:40 -0500 [thread overview]
Message-ID: <3882F748.503E34A4@yahoo.com> (raw)
In-Reply-To: Pine.SGI.4.10.10001141230510.254646-100000@brule.borg.umn.edu
>
> Niklaus (and others),
>
> Thanks again for the insight on the Oak 8390-based Ethernet driver. The
> polled register read/write macros did the trick (at least partially so).
>
> I've done the modification fairly cleanly; however, I'm not sure that the
> kernel maintainers will accept the attendant changes to 8390.[ch] via the
> nic_{i,o}[s]{b,w}[p] macros. We'll see.
Hard to say without seeing it. Not worth bending over backwards to try
and adapt the current 8390 if it means obfuscating things in the process
(the EI_SHIFT trickery may lie somehwere in this grey area). Code
duplication is no longer considered supreme evil (wrt linux drivers
anyway)
if it makes life easier.
> The board now at least ARPs through the interface to the NFS server and
> the NFS server responds. However, that's as far as it gets at this point
> (see below). Any ideas? In the interim, I'm going to try experimenting
> with a few more things.
Sounds like your driver isn't Rx'ing the arp reply properly and handing
it off to the upper layers where it can get put into the ARP table.
I assume /proc/net/arp isn't showing your NFS server.
What is the scoop on these cards? At a glance oaknet.c in 2.3.40 looks
pretty much like ne.c but stripped of the PCI crud.
Paul.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-17 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s87e4deb.081@netstal.com>
2000-01-14 19:29 ` Help Sought: 8390-Ethernet Troubles on PowerPC 4xx Port Grant Erickson
2000-01-17 11:04 ` Paul Gortmaker [this message]
[not found] <s87fa3ee.073@netstal.com>
2000-01-14 22:12 ` Grant Erickson
2000-01-13 1:10 Grant Erickson
2000-01-13 6:53 ` Magnus Damm
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=3882F748.503E34A4@yahoo.com \
--to=p_gortmaker@yahoo.com \
--cc=grant@lcse.umn.edu \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=n.giger@netstal.com \
/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;
as well as URLs for NNTP newsgroup(s).