On Wed, Oct 04, 2006 at 09:49:39AM +0200, Johannes Berg wrote:
> On Tue, 2006-10-03 at 19:16 -0400, Theodore Tso wrote:
>
> > OK, I'm going to ask a stupid question. Why is the kernel<->wireless
> > driver interface have to be tied to the userspace<->wireless
> > interface?
>
> Haha. Because Jean thinks it isn't and thus everything is fine. But in
> reality it is.
>
> > Is there some reason why this would be too hard to do with the current
> > interface?
>
> Yes: drivers are expected to mostly handle the ioctls directly without a
> layer between them and userspace.
Once again, your facts are totally wrong about Wireless
Extensions.
Have you ever looked at the code in the kernel ? I guarantee
you that adding whatever specific WE translation is quite easy. In
this precise case, this would only increase confusion, so this should
be considered bad API practice.
Regards,
Jean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
- Re: wpa supplicant/ipw3945, ESSID last char missing
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]