Re: [RFC] Wireless extensions rethink

[Jean Tourrilhes <jt@xxxxxxxxxxxxxxxxxx>]

On Thu, Jun 17, 2004 at 04:06:25PM -0400, Jeff Garzik wrote:
> 
> >>The general API, yes.  But most driver-private interfaces will fail 
> >>miserably through 32/64-bit translation.
> >
> >
> >     That's fixable, and easy to fix, if needed. You have all the
> >data you need in the kernel.
> 
> Not really -- it's the same problem as SIOCDEVPRIVATE.  Driver-private 
> interfaces by definition change for each driver.  Translation of the 
> same ioctl differs on a per-driver basis.  Consider what happens when 
> passing pointers from userland, for example...

        I can assure you that I thought about that precise issue when
I re-designed the API in 91. I confirm that all the necessary data in
the kernel to do this properly.
        Proof : the "copy_to/from_user" is done in the generic code,
not in the driver. The driver export to the generic code all the data
needed to know where are those user pointers. What else is needed ?

> It was for this reason that we created the MII ioctls, which were 
> previously SIOCDEVPRIVATE.

        Totally different business. Those ioctls were totally
anonymous, with no meta-data.

>       Jeff

        Jean