> 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
struct atm_physical
struct dsl_physical
struct dsl_bitstream
struct tr_physical
struct wireless_physical
struct wireless_80211
struct wireless_auth
} config;
}
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
- Re: [RFC-2] Configuring Synchronous Interfaces in Linux Matthew G. Marsh
- Re: [RFC-2] Configuring Synchronous Interfaces in Linux Paul Fulghum
- Re: [RFC-2] Configuring Synchronous Interfaces in Linux Ivan Passos
- Re: [RFC-2] Configuring Synchronous Interfaces in Linux Stuart Lynne
- Re: [RFC-2] Configuring Synchronous Interfaces in Li... Alan Cox
- Re: [RFC-2] Configuring Synchronous Interfaces i... Dan Hollis
- Re: [RFC-2] Configuring Synchronous Interfac... Stuart Lynne
- Re: [RFC-2] Configuring Synchronous Interfaces i... Krzysztof Halasa
- Re: [RFC-2] Configuring Synchronous Interfac... Alan Cox
- Re: [RFC-2] Configuring Synchronous Inte... Jeff Garzik
- Re: [RFC-2] Configuring Synchronous... Alan Cox
- parport0 problem ebi4
- Re: [RFC-2] Configuring Synchronous Inte... Krzysztof Halasa

