[First version of this mail seems to have gotten lost. Apologies if you see it twice] Some distributions call iwconfig at every bootup and I was sick of seeing all the unimplemented ioctl messages on
Went it in after 2.6.1? 2.6.1 definitely spews out warnings for it at every boot, that is why I did this. If it's already fixed that's fine for me of course. -Andi
Oh, I actually posted it yesterday but due a broken MTA it didn't go out @) But I didn't check BK anyways so it would not have made much difference. -Andi
I'm glad that you found the ioctl description table useful, the code look neat and simple. When I did redesign the driver API in WE-13, ioctl emulation for 64 bits was definitely on my mind (thanks t
I don't use wireless at all[1] - I was just annoyed at the storm of unimplemented ioctl messages when booting up 32bit userland. SuSE 9.0 boot up calls iwconfig by default. [1] I actually have a Sams
I was wondering, because Samsungs cards should be supported by the HostAP driver (which remind me, HostAP needs to go in the kernel). This analogy doesn't work. If your network is wireless, you won't
It apparently works with David Hinds' PCMCIA kit, but that is far too messy to patch into a changing development kernel all the time. The main problem seems to be the missing bridge support in the ke
I think the situation is different. On several 64-bit platforms we encourage using 32-bit compilation and binaries by default because: 1) they're a lot faster than their 64-bit counterparts 2) they'r
Just for the record: this doesn't apply to AMD64. While data structures take a bit more memory at runtime the 64bit code is a lot better due to more registers and better ABI. And it is also not sign
I see you have it covered : http://www.ussg.iu.edu/hypermail/linux/kernel/0312.1/0469.html You may want to get in touch with Dominik Brodowski and Russell King, because the i82365 driver in 2.6.X is
[First version of this mail seems to have gotten lost. Apologies if you see it twice] Some distributions call iwconfig at every bootup and I was sick of seeing all the unimplemented ioctl messages on
Went it in after 2.6.1? 2.6.1 definitely spews out warnings for it at every boot, that is why I did this. If it's already fixed that's fine for me of course. -Andi