linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel L. Taylor" <Dan.Taylor@atlp.com>
To: Torben Mathiasen <torben@kernel.dk>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: eepro100 on IBM Walnut board,
Date: Thu, 05 Apr 2001 15:31:28 -0700	[thread overview]
Message-ID: <3ACCF240.63E65D44@atlp.com> (raw)
In-Reply-To: 20010405212019.H1475@fry


We've been using the Intel-supplied driver

http://support.intel.com/support/network/adapter/pro100/30504.htm

with an MPC8240.  We've noticed that the driver in all current
kernels is "problematic", at best, even on x86 (there used to be
a usable one, but I haven't seen it in any tree, lately).

Hope this helps.

Torben Mathiasen wrote:
>
> Hi,
>
> 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.
>
> Thanks in advance,
>
> Torben
>

--
Dan.Taylor@atlp.com

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2001-04-05 22:31 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
2001-04-06  9:05   ` Matt Porter
2001-04-05 22:31 ` Daniel L. Taylor [this message]
  -- 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=3ACCF240.63E65D44@atlp.com \
    --to=dan.taylor@atlp.com \
    --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).