From: Catalin Marinas <catalin.marinas@arm.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Netdev List <netdev@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Russell King <rmk+lkml@arm.linux.org.uk>,
"Kok, Auke" <auke-jan.h.kok@intel.com>
Subject: Re: [RFT] e100 driver on ARM
Date: Mon, 04 Sep 2006 15:34:14 +0100 [thread overview]
Message-ID: <tnxk64jr995.fsf@arm.com> (raw)
In-Reply-To: <44FC0261.6010807@garzik.org> (Jeff Garzik's message of "Mon, 04 Sep 2006 06:39:29 -0400")
Jeff Garzik <jeff@garzik.org> wrote:
> The eepro100 removal has been blocked for almost a year by a vague
> suggestion from Russell that e100 doesn't work on ARM. But he doesn't
> have that machine anymore. So, we're stuck in limbo.
Russell might have tested it on an Integrator/AP (not sure
though). IIRC, I tested the e100.c driver on this platform with 2.6.12
and it was OK at that time (the platform is now discontinued by ARM
Ltd).
> 1) Does e100 driver work on ARM?
I tested the e100.c driver a few months ago on the Versatile/PB and
RealView/EB platforms with PCI backplanes attached. The driver seemed
to work well (after fixing some PCI hardware problems on our
platforms). I couldn't get the eepro100.c driver to work though, but
didn't have any reason to investigate further.
--
Catalin
prev parent reply other threads:[~2006-09-04 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 10:39 [RFT] e100 driver on ARM Jeff Garzik
2006-09-04 12:31 ` Lennert Buytenhek
2007-03-28 23:04 ` Kok, Auke
2007-03-29 5:17 ` David Acker
2007-03-29 14:10 ` Lennart Sorensen
2007-04-16 15:07 ` David Acker
2007-04-17 17:35 ` Lennart Sorensen
2007-04-26 13:41 ` David Acker
2007-04-26 13:50 ` Lennert Buytenhek
2007-04-26 15:12 ` Jeff Garzik
2007-04-26 15:40 ` Kok, Auke
2007-04-26 16:09 ` Jeff Garzik
2007-04-26 16:20 ` Kok, Auke
2007-04-26 16:19 ` H. Peter Anvin
2007-04-27 19:01 ` Lennart Sorensen
2006-09-04 14:34 ` Catalin Marinas [this message]
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=tnxk64jr995.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.