Re: [Lcd4linux-devel] plugin_wifi ?

[Xavier V. <xav...@fr...>]

Helli Martin !

> > I use 2.6 since 2.6.2 and never had big
> > problems with it (just one: vmware didn't worked, but I didn't use it)
> Well, for me, vmware is one of the show-stoppers (I don't really want to 
> have to back to dual-booting or having another computer under my desk). 
> And please, lets not get into the "what do you need windows for? Linux 
> can do everything" discussion - lets just assume that there is a need 
> for me to run windows at home, even if I prefer Linux most of the time.
In fact, the old version I had didn't support 2.6, but new versions do
 (hopefully) support 2.6 ! But as I didn't use it anymore, I didn't
 searched for an upgrade on *mule :)

> >> or go ahead and code the wifi plugin for 2.6, and I'll code a 2.4
> >> plugin for the rest of us).
> > Maybe it would be the best solution if ioctl are too complicated. Each
> > would be quite easy to code (one based on plugin_netdev, the other based
> > on i2c_sensors) while the ioctl one would be quite hard to code, IMHO
> I don't really see why it would be terribly hard to code - but I haven't 
> had time to look at it in detail yet.
I digged into wireless-tools source, and here is what to do :
- open a socket : socket(AF_INEL, SOCK_DGRM, 0)
- check if the interface has wireless extensions (SIOCGIWNAME ioctl)
- get the statistics (SIOCGIWSTATS ioctl)
- handle the iw_statistics struct, which contains itself structs, and
parse the info.
It is easier than I expected.

> I'm not quite sure why it would imply more memory "problems" (I'm not 
> even sure what you're referring to actually - do you mean memory usage? 
> "memory problems" imply a bug to me).
It's both a little more memory usage, but moreover, manipulating
struct->struct->__u32 variables may get quite messy :/
I'll try to code a test.

Bye !
-- 
Xavier VELLO <xav...@fr...>