Searched refs:authenticate (Results 1 – 4 of 4) sorted by relevance
| /drivers/staging/greybus/ |
| A D | authentication.c | 242 size = sizeof(*authenticate); in cap_ioctl()
243 authenticate = memdup_user(buf, size); in cap_ioctl()
244 if (IS_ERR(authenticate)) in cap_ioctl()
245 return PTR_ERR(authenticate); in cap_ioctl()
248 authenticate->uid, in cap_ioctl()
249 authenticate->challenge, in cap_ioctl()
250 &authenticate->result_code, in cap_ioctl()
251 authenticate->response, in cap_ioctl()
252 &authenticate->signature_size, in cap_ioctl()
253 authenticate->signature); in cap_ioctl()
[all …]
|
| /drivers/staging/greybus/Documentation/firmware/ |
| A D | authenticate.c | 24 struct cap_ioc_authenticate authenticate = { variable
78 memcpy(authenticate.uid, uid.uid, 8); in main()
80 ret = ioctl(fd, CAP_IOC_AUTHENTICATE, &authenticate); in main()
88 authenticate.result_code, authenticate.signature_size); in main()
|
| A D | firmware-management | 188 directory and will be named gb-authenticate-<N>. The number <N> is assigned at
195 gb-authenticate-N and user first needs to identify the character device used for
204 /sys/bus/greybus/devices/1-1/1-1.1/1-1.1.1/gb_authenticate/gb-authenticate-0
206 The last name in this path: gb-authenticate-0 is precisely the name of the char
209 /dev/gb-authenticate-0.
214 The Character device (/dev/gb-authenticate-0 in above example) can be opened by
299 This ioctl shall be used by the user to authenticate the Module attached to
331 The current directory also provides a authenticate.c test application, which can
|
| /drivers/block/drbd/ |
| A D | Kconfig | 16 NOTE: In order to authenticate connections you have to select
|
Completed in 7 milliseconds