>> the reason that we use IOCTL is that we need to "associate" (Connect) >> the current file description to a FW Client/Feature. (opening a comm >> channel) . > >As you didn't document this ioctl interface anywhere, saying exactly what you >are trying to do, it makes it a bit hard to review your existing interface to >determine that ioctls are the correct thing for your device. >Care to document it, or at least describe it in the patches somewhere so we >know it and can properly review it? In the header file that I defined the IOCTL, I put a comment that describing the IOCTL. Also in patch0 there is description about the use case of this IOCTL. Tell me what kind of information you think that are missing and I will add it. If needed I will add more information. > >> and in addition there is a security issue that we would like limit the >> access to mei driver to system admins. >> >> From what I read we can't get those requirements with Netlinks, right? >> If there other methods for achieving this ? > >sysfs, configfs, your own filesystem, etc. There are lots of options. Great, we are willing to hear any suggestions that people. I'm willing to provide any information about the driver that is needed for the discussion. . --- Oren Weil - Intel Corporation. http://www.intel.com
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
--------------------------------------------------------------------- Intel Israel (74) Limited This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
