Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 20 Feb 2003 20:40:13 -0500 | From | Jeff Garzik <> | Subject | Re: ioctl32 consolidation |
| |
Max Krasnyansky wrote: > Hmm. It seems to that all you need for SIOCDEVPRIVATE is ability to register > ranges of ioctls. > i.e. something like this > int register_ioctl32_conversion_rage(uint start, uint end, handler); > > net/core/dev.c > register_ioctl32_conversion_range(SIOCDEVPRIVATE, SIOCDEVPRIVATE + 15, siocdevprivate_ioctl); > > Am I missing something here ?
Yes. Think about the name of the ioctl :)
It is impossible for generic arch code to implement support for driver-private ioctls, because these naturally differ between each driver.
Jeff
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |