From: Bill Fincke <willy@synergymicro.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: "broken" GT64260 ethernet driver
Date: Fri, 10 May 2002 10:13:46 -0700 [thread overview]
Message-ID: <3CDBFFC9.205DB0A5@synergymicro.com> (raw)
In-Reply-To: 200205100459.XAA27925@lists.linuxppc.org
I have ported the gt64260_eth.c driver (from the MontaVista BK
tree) to our board. The only modifications made were for our MAC
address setup and interrupt connections. I have run all 3 ports
under 2.4.12-SMP and have not yet seen a problem, but I haven't
done anything too stressful.
But there have been a lot of "this driver is broken" comments
on the thread. I agree it's ugly, but it seems to work. Can
someone elaborate on exactly what is "broken", so I can test
it more thoroughly?
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-05-10 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200205100459.XAA27925@lists.linuxppc.org>
2002-05-10 17:13 ` Bill Fincke [this message]
2002-05-10 17:24 ` "broken" GT64260 ethernet driver mod+linuxppc-dev
2002-05-10 17:30 ` Mark A. Greer
2002-05-31 0:53 ` GT64260 ethernet driver - long term stability? Bill Fincke
2002-05-31 11:21 ` Geert Uytterhoeven
2002-05-31 21:52 ` Mark A. Greer
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=3CDBFFC9.205DB0A5@synergymicro.com \
--to=willy@synergymicro.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).