All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Krzysztof Halasa <khc@intrepid.pm.waw.pl>, linux-kernel@vger.kernel.org
Subject: Re: [RFC-2] Configuring Synchronous Interfaces in Linux
Date: Thu, 07 Dec 2000 09:12:36 -0500	[thread overview]
Message-ID: <3A2F9AD4.830153B4@mandrakesoft.com> (raw)
In-Reply-To: <E1441je-0002T3-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > I think we need few ioctl calls: get + set media (int argument),
> > get + set speed (probably two - RX and TX), etc.
> > In my 2.4 HDLC stuff - to be published :-( - there something like that
> > (in private ioctl range, of course).
> 
> I think we are agreeing
> 
> I'm saying use something like
> 
>         struct
>         {
>                 u16 media_group;
>                 union
>                 {
>                         struct hdlc_physical ...
>                         struct hdlc_bitstream
>                         struct hdlc_protocol
>                         struct fr_protocol
>                         struct eth_physical

Not yet another one for eth...  We now have ethtool for this.  And a
generic netdevice::set_config wrapper can be created that simply calls
the ethtool ioctl with the proper info and locking.

	Jeff


-- 
Jeff Garzik         |
Building 1024       | These are not the J's you're lookin' for.
MandrakeSoft        | It's an old Jedi mind trick.
-
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-07 14:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-05 22:55 [RFC-2] Configuring Synchronous Interfaces in Linux Stuart Lynne
2000-12-06  1:21 ` Alan Cox
2000-12-06  1:34   ` Dan Hollis
2000-12-06  1:55     ` Stuart Lynne
2000-12-07  0:14   ` Krzysztof Halasa
2000-12-07 14:09     ` Alan Cox
2000-12-07 14:12       ` Jeff Garzik [this message]
2000-12-07 14:40         ` Alan Cox
2000-12-09 22:33           ` parport0 problem ebi4
2001-03-19 16:28       ` [RFC-2] Configuring Synchronous Interfaces in Linux Krzysztof Halasa
     [not found] <Pine.LNX.4.30.0012051925330.6718-100000@pc24.sr.bham.ac.uk>
2000-12-05 19:46 ` Ivan Passos
  -- strict thread matches above, loose matches on Subject: below --
2000-12-05  5:58 Ivan Passos
2000-12-05  9:38 ` Francois Romieu
2000-12-05 19:17   ` Ivan Passos
2000-12-05  9:41 ` Alan Cox
2000-12-05 15:15   ` Greg Parrott
2000-12-05 19:23   ` Ivan Passos
2000-12-05 20:41     ` Peter Samuelson
2000-12-05 21:56     ` Alan Cox
2000-12-05 14:43 ` Matthew G. Marsh
2000-12-05 19:40   ` Ivan Passos
2000-12-05 15:18 ` Paul Fulghum

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=3A2F9AD4.830153B4@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=khc@intrepid.pm.waw.pl \
    --cc=linux-kernel@vger.kernel.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 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.