| To: | Jeff Garzik <jgarzik@xxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC] Wireless extensions rethink |
| From: | Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx> |
| Date: | Wed, 16 Jun 2004 16:11:13 -0700 |
| Address: | HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA. |
| Cc: | Gertjan van Wingerde <gwingerde@xxxxxxx>, sfeldma@xxxxxxxxx, netdev@xxxxxxxxxxx, jkmaline@xxxxxxxxx |
| E-mail: | jt@xxxxxxxxxx |
| In-reply-to: | <40D0D265.3070804@xxxxxxxxx> |
| Organisation: | HP Labs Palo Alto |
| 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> |
| Reply-to: | jt@xxxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Wed, Jun 16, 2004 at 07:06:13PM -0400, Jeff Garzik wrote:
> Jean Tourrilhes wrote:
> > I think you did not understood my idea at all.
> > If you build a set of generic wrappers and hook them in the
> >iw_handler table, you could trivially add the features you feel are
> >missing into those wrappers. Those wrappers would expose whatever API
> >you choose to the driver, call your struct wireless_ops for example.
>
> That doesn't help anything. Wrappers add code, while not solving the
> following problems...
You need to start somewhere. This allow you to experiment with
the API simply until you get it to the point you like it.
Jean
|
| Previous by Date: | Re: IPsec and Path MTU, Herbert Xu |
|---|---|
| Next by Date: | Re: RFC: Cisco HDLC bridging, Krzysztof Halasa |
| Previous by Thread: | Re: [RFC] Wireless extensions rethink, Jeff Garzik |
| Next by Thread: | Re: [RFC] Wireless extensions rethink, Jean Tourrilhes |
| Indexes: | [Date] [Thread] [Top] [All Lists] |