| To: | prism54-devel@xxxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH/RFC] set_rates support for prism54 |
| From: | margitsw@xxxxxxxxxxx (Margit Schubert-While) |
| Date: | Sun, 15 Aug 2004 21:10:05 +0200 |
| Cc: | vda@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx, mcgrof@xxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx, jgarzik@xxxxxxxxx |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Denis scribeth: > Ok. And then we will need to parse that data into format suitable for > prism54 in prism54 driver, and into format suitable for acx100/acx111 > in acx100 driver, etc... No, no. The format as it arrives at the driver should be fixed/defined. Exactly as happens to private ioctls now. Let's, for the sake of argument, say that we misuse the iw_freq structure. (We can/should define a new structure) iwpriv parses and sets up an iw_freq structure in the buffer that it passes for -each- rate. eg: freq.i = rate freq.m = modulation freq.e = basic/extended So, the driver gets a bunch of defined structures to act upon. Margit |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Prism54-devel] Re: [PATCH/RFC] set_rates support for prism54, Denis Vlasenko |
|---|---|
| Next by Date: | Re: kernel-2.6.8.1 EIP is at velocity_netdev_event+0x16/0x50, George Georgalis |
| Previous by Thread: | Re: [Prism54-devel] Re: [PATCH/RFC] set_rates support for prism54, Denis Vlasenko |
| Next by Thread: | Re: [Openswan Users] Invalid argument NULL, Herbert Xu |
| Indexes: | [Date] [Thread] [Top] [All Lists] |