Hi Luca, > after having had a rapid look at UVC driver internals, I saw that the > read() system call has not been implemented yet, while poll() is > implemented and can be called from userspace. > > Apart from the V4L2 API, given that poll() is a standard > system call and is supposed to be closely tied to non-blocking reads() > to provide a _standard_ I/O mechanism for retrieving data, are there > any reasons for not providing read() as well together with poll(), > as it's probably confusing to have partial support for this > I/O interface?
The only reason why read() hasn't been implemented (yet) is that mmap() has been implemented first, and there hasn't been any demand for read(). It's on my todo list though. poll() without read() makes sense, using VIDIOC_DQBUF. Best regards, Laurent Pinchart _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
