From: Chris Wedgwood <cw@f00f.org>
To: Donald Becker <becker@scyld.com>
Cc: Francois Romieu <romieu@cogenit.fr>,
Russell King <rmk@arm.linux.org.uk>,
Ivan Passos <lists@cyclades.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC] Configuring synchronous interfaces in Linux
Date: Sun, 3 Dec 2000 07:59:58 +1300 [thread overview]
Message-ID: <20001203075958.A1121@metastasis.f00f.org> (raw)
In-Reply-To: <20001201140042.A8572@se1.cogenit.fr> <Pine.LNX.4.10.10012021041460.16980-100000@vaio.greennet>
In-Reply-To: <Pine.LNX.4.10.10012021041460.16980-100000@vaio.greennet>; from becker@scyld.com on Sat, Dec 02, 2000 at 11:09:35AM -0500
On Sat, Dec 02, 2000 at 11:09:35AM -0500, Donald Becker wrote:
On Fri, 1 Dec 2000, Francois Romieu wrote:
> Russell King <rmk@arm.linux.org.uk> écrit :
> [...]
> > We already have a standard interface for this, but many drivers do not
> > support it. Its called "ifconfig eth0 media xxx":
Uhmmm, it's not a standard if "many drivers do not support it".
It is very easy to hack up code to handle one or two drivers.
But you shouldn't claim the problem is fixed until the approach is tested
with all of the driver.
Hey, I'll make it easy. Find an approach that fully handles only the Tulip
and 3c59x drivers, and that is consistent.
Actually, I starteed work on adding this to the 3c59x code last
night; I am now a little dispondent though as it wasn't as simple as
I first thought it might be.
I am now wondering whether it make sense to break 3c59x into smaller
peices which hander fewer cards each; there soom to be many things
the driver knows about which probably don't relate to my needs.
--cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-02 19:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 19:16 [RFC] Configuring synchronous interfaces in Linux Ivan Passos
2000-12-01 9:01 ` Francois romieu
2000-12-01 10:32 ` Chris Wedgwood
2000-12-01 11:00 ` Christoph Hellwig
2000-12-01 12:30 ` Xavier Bestel
2000-12-01 12:07 ` Russell King
2000-12-01 13:00 ` Francois Romieu
2000-12-02 16:09 ` Donald Becker
2000-12-02 18:59 ` Chris Wedgwood [this message]
2000-12-02 19:07 ` Jeff Garzik
2000-12-02 19:46 ` Russell King
2000-12-02 20:02 ` Philip Blundell
2000-12-03 5:47 ` Chris Wedgwood
2000-12-03 11:10 ` Philip Blundell
2000-12-03 11:27 ` Russell King
2000-12-03 0:20 ` Keith Owens
2000-12-03 13:43 ` Jeff Garzik
2000-12-03 20:29 ` Keith Owens
2000-12-03 20:41 ` Keith Owens
2000-12-02 19:48 ` Donald Becker
2000-12-07 8:44 ` Chris Wedgwood
2000-12-01 13:44 ` Philip Blundell
2000-12-01 12:15 ` Francois Romieu
2000-12-01 13:14 ` Bogdan Costescu
2000-12-01 16:26 ` Francois Desloges
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=20001203075958.A1121@metastasis.f00f.org \
--to=cw@f00f.org \
--cc=becker@scyld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@cyclades.com \
--cc=netdev@oss.sgi.com \
--cc=rmk@arm.linux.org.uk \
--cc=romieu@cogenit.fr \
/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.