Messages in this thread | | | Date | Wed, 1 Feb 2006 15:19:40 +0100 | From | Aritz Bastida <> | Subject | Re: Right way to configure a driver? (sysfs, ioctl, proc, configfs,....) |
| |
Hi!
> At the risk of the obvious.... > > struct meminfo meminfo; > ioctl(fd, UPDATE_PARAMS, &meminfo); > > ... and define UPDATE_PARAMS and other function codes to start > above those normally used by kernel stuff so that `strace` doesn't > make up stories. > > This is what the ioctl() interface is for. Inside the kernel > you can use spinlocks (after you got the data from user-space) > to make the operations atomicc. >
Well, actually that's more or less what I had done before, and it worked. I had a group of ioctl commands for configuring my device. The command number was based on an unusded "magic number", as I was told when reading Linux Device Drivers 3rd:
#define SCULL_IOCSQUANTUM _IOW(SCULL_IOC_MAGIC, 1, int) #define SCULL_IOCSQSET _IOW(SCULL_IOC_MAGIC, 2, int)
This actually works, but it doesnt seem to be "ellegant" code for new drivers in 2.6. Or at least that's what it says in LDD3, since the ioctls are system wide, unstructured, and so on.
That's why I was asking for a more ellegant and cleaner configuration method. It seems that the new filesystem "configfs" is perfect for that, but I would like to know if netlink sockets can also be used for that purpose (as I'm writing a kind of network device).
Thank you anyway Regards
Aritz - 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/
| |