public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: romieu@ensta.fr
Cc: Ivan Passos <lists@cyclades.com>,
	linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC] Configuring synchronous interfaces in Linux
Date: Fri, 1 Dec 2000 23:32:27 +1300	[thread overview]
Message-ID: <20001201233227.A9457@metastasis.f00f.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10011301103320.4692-100000@main.cyclades.com> <20001201100124.A4986@se1.cogenit.fr>
In-Reply-To: <20001201100124.A4986@se1.cogenit.fr>; from romieu@cogenit.fr on Fri, Dec 01, 2000 at 10:01:24AM +0100

On Fri, Dec 01, 2000 at 10:01:24AM +0100, Francois romieu wrote:

    > Questions:
    > - Is there any existing _standard_ interface to do that??
    
    No.

[...]

    > I'm interested in implementing this, but I don't want to reinvent the
    > wheel (if such wheel exists ...).
    
    Ditto.


Actually; Ethernet badly needs something like this too. I would kill
to be able to do something like:

	ifconfig eth0 speed 100 duplex full

o across different networks cards -- I've been thinking about it of
late as I had to battle with this earlier this week; depending on
what network card you use, you need different magic incarnations to
do the above.

A standard interface is really needed; unless anyone objects I may
look at drafting something up -- but it will require some input if it
is not to look completely Ethernet centric.



  --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/

  reply	other threads:[~2000-12-01 11:03 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 [this message]
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
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=20001201233227.A9457@metastasis.f00f.org \
    --to=cw@f00f.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@cyclades.com \
    --cc=netdev@oss.sgi.com \
    --cc=romieu@ensta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox