> > 3.- Actually the most difficult config I must do is to pass three
> > values from userspace to my module. Specifically two integers and a
> > long (it's an offset to a memory zone I've previously defined)
> >
> > struct meminfo {
> > unsigned int id; /* segment identifier */
> > unsigned int size; /* size of the memory area */
> > unsigned long offset; /* offset to the information */
> > };
> >
> > How would you pass this information in sysfs? Three values in the same
> > file? Note that using three different files wouldn't be atomic, and I
> > need atomicity.
>
> Use configfs.
>
Ummhh, and would it be correct to configure my device via a netlink
socket? Remember that my driver is a kind of network "virtual" device.
There are so many old and new ways to configure a driver that I'm a
bit overwhelmed...
Regards
Aritz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Right way to configure a driver? (sysfs, ioctl, proc, configfs,....)
- Re: Right way to configure a driver? (sysfs, ioctl, proc, configfs,....)
- Re: Right way to configure a driver? (sysfs, ioctl, proc, configfs,....)
- Re: Right way to configure a driver? (sysfs, ioctl, proc, configfs,....)
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]