From: "Ron Bianco" <ronb@junction.net>
To: "Torben Mathiasen" <torben@kernel.dk>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: RE: eepro100 on IBM Walnut board,
Date: Thu, 5 Apr 2001 15:47:40 -0700 [thread overview]
Message-ID: <001601c0be22$6b8ecca0$4d012ac7@warp-speed> (raw)
In-Reply-To: <20010405143318.E1889@ftsoj.fsmlabs.com>
Didn't have endian problems in the version we're using on our PPC 8240 board.
The version string says: eepro100.c:v1.09j 7/27/99 Donald Becker.......etc.
I had problems with newer versions, I think endian issues were one of the them.
Ron
> -----Original Message-----
> From: owner-linuxppc-embedded@lists.linuxppc.org
> [mailto:owner-linuxppc-embedded@lists.linuxppc.org]On Behalf Of Cort
> Dougan
> Sent: Thursday, April 05, 2001 1:33 PM
> To: Torben Mathiasen
> Cc: linuxppc-embedded@lists.linuxppc.org
> Subject: Re: eepro100 on IBM Walnut board,
>
>
>
> The latest eepro has serious endian-ness problems. PPC and MIPS suffer
> this problem.
>
> } Has anyone tried using an Intel i82559 NIC as a second adapter with an IBM Walnut board? I'm using the
> eepro100 driver
> } with the montavista distribution (tried 2.4.0-test2 and 2.4.2) and the driver just keeps printing:
> wait_for_cmd_timeout.
> } The NIC won't send any frames, and no interrupts are generated.
> }
> } The docs claim that the eepro100 driver should work.
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-05 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 19:20 eepro100 on IBM Walnut board, Torben Mathiasen
2001-04-05 20:33 ` Cort Dougan
2001-04-05 22:47 ` Ron Bianco [this message]
2001-04-06 9:05 ` Matt Porter
2001-04-05 22:31 ` Daniel L. Taylor
-- strict thread matches above, loose matches on Subject: below --
2001-04-06 10:16 Mathiasen, Torben
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='001601c0be22$6b8ecca0$4d012ac7@warp-speed' \
--to=ronb@junction.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=torben@kernel.dk \
/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).