[lkml]   [2003]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: two x86_64 fixes for 2.4.21-pre3
On Mon, Feb 03, 2003 at 09:12:55PM +0100, Andi Kleen wrote:
> >
> > Why don't you just recompile the Wireless Tools (iwconfig and
> > friends) for 64 bits ?
> We normally try to at least support all ioctls which are used in
> standard distributions as 32bit. This way users can easily switch
> between 32bit and 64bit userland. The coverage is very good
> (standing on the shoulders of sparc64 emulation gigants).

In this case, the degradation is quite graceful. The Wireless
Tools just assume that the card doesn't support Wireless Extension, so
you won't get extra stats and configuration, but you can still use the

> Of course 64bit tools exist, just the 64bit distributions are not commonly
> available yet and it's still nice to switch at will.

I believe that *BSD consider all system tools as part of the
base OS, and is compiled alongside the kernel, so you don't have this
issue, because kernel and tools are "in sync".
Anyway, I believe that 64 bit platforms will need to become
mainstream before the issue of wireless on 64 bit is pressing, and by
that time most distro will have made the jump.

> > With regards to this specific problem, just return an
> > error. The Wireless Tools should gracefully handle it and report to
> That is currently done (-EINVAL), but the emulation layer logs an
> warning.

It's just a shame that it's not more distinctive, because the
error message wouldn't lead me to think "doh, I need a recompile".

> > Just food for thought... I you think the wireless ioctls are
> > bad, there is worse. The linux-wlan-ng driver defines it's own driver
> > specific ioctls, and it has 3 times the number of ioctls. Just for one
> > driver. And the ioctl format sometimes changes with revision.
> That's bad. Do they at least have unique numbers?

They use the device private ioctls and subclass them. They use
one ioctl to query the driver for support of the API.

> > So, clearly you can't expect to deal with every ioctl under
> > the sun, that's just not practical.
> So far it works.

Of course, because you have dealt with the most common
subset. I want to remain pragmatic and try to define how far we need
to go. 100% coverage is unrealistic, and there is always the tradeof
between amount of work and number of users.
I just believe that in thise case the number of users is not
there yet, and we can re-evaluate our options when we have those
users, because at that point we may have new options available.

Also note that I made a first step in your direction. Since
WE-13, most of the metadata describing the ioctls is in the kernel
itself and the copy_to/from_user is centralised, which should make
things easier once all drivers are converted...

> -Andi

Have fun...

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:32    [W:0.088 / U:11.964 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site