netdev
[Top] [All Lists]

Re: [RFC] Wireless extensions rethink

To: Jeff Garzik <jgarzik@xxxxxxxxx>
Subject: Re: [RFC] Wireless extensions rethink
From: Gertjan van Wingerde <gwingerde@xxxxxxx>
Date: Thu, 17 Jun 2004 20:30:40 +0200
Cc: netdev@xxxxxxxxxxx, jt@xxxxxxxxxx, sfeldma@xxxxxxxxx, jkmaline@xxxxxxxxx
In-reply-to: <40D1E24C.8090802@xxxxxxxxx>
References: <C6F5CF431189FA4CBAEC9E7DD5441E0103AF626C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <40CF263E.70009@xxxxxxx> <1087377197.25912.54.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <40D08769.3070106@xxxxxxx> <20040616204248.GA23617@xxxxxxxxxxxxxxxxxx> <40D0BD5B.201@xxxxxxxxx> <20040616223316.GA29618@xxxxxxxxxxxxxxxxxx> <40D0D265.3070804@xxxxxxxxx> <20040617174717.GA30460@xxxxxxxxxxxxxxxxxx> <40D1E185.2010201@xxxxxxxxx> <40D1E24C.8090802@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.6 (X11/20040526)
Jeff,

I think I get the gist of it. I'll start working on this and produce some 
results in a few days.
We can then review the results start discussing further 
directions/modifications.

I'll leave netlink out of it right now (see the problems Jean had earlier), but 
I think that the
basic approach (wireless_ops, etc.) can be reused within a netlink 
implementation anyway.

--- Gertjan.


Jeff Garzik wrote:
Jeff Garzik wrote:

struct wireless_ops {
int (*get_name) (struct net_device *dev, struct iw_request_info *info,
                           union iwreq_data *wrqu, char *extra);
int (*get_freq) (struct net_device *dev, struct iw_request_info *info,
                               union iwreq_data *wrqu, char *extra);
int (*set_freq) (struct net_device *dev, struct iw_request_info *info,
                           union iwreq_data *wrqu, char *extra);
int (*get_mode) (struct net_device *dev, struct iw_request_info *info,
                           union iwreq_data *wrqu, char *extra);
int (*set_mode) (struct net_device *dev, struct iw_request_info *info,
                           union iwreq_data *wrqu, char *extra);



Note that the above is only a first step. Through the standard Linux development process -- evolution -- each hook can be pared down to precisely what each call needs. The above allows for a quick transition of drivers, while keeping them working.

    Jeff





<Prev in Thread] Current Thread [Next in Thread>