From: Jon Masters <jonmasters@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: smc91111
Date: Mon, 4 Oct 2004 23:28:26 +0100 [thread overview]
Message-ID: <35fb2e5904100415285979b343@mail.gmail.com> (raw)
Hi all,
I've got a hacked version of the smc91111 driver from an old arm tree
that I'm happily using on my board at work - I'll post patches for it
in due course as we use a custom 16bit bus that physically looks and
acts like ISA (but really is cunningly slightly different in timing
and spec as it's a soft core implemented bridge bodged together to
work on a dev board. mmmmmm.).
Today I had to add some ethtool support to the driver to support using
howl (anybody else use that to do Zero Conf?) and was debating fixing
up http://criticalmass.sourceforge.net/kernel/smc91x/ to work with odd
bus types like ours (it's a lot of work and testing compared with a
quick hack to get this done on time so this question is more
hyperthetical when I'm done with the immediate problem).
Who is using the SMC91111 family of MACs and if so which driver do you use?
Jon.
next reply other threads:[~2004-10-04 22:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 22:28 Jon Masters [this message]
2004-10-05 20:51 ` smc91111 Dale Farnsworth
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=35fb2e5904100415285979b343@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linuxppc-embedded@ozlabs.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).