> Not sure how to handle the ioctl translation best. The problem is where > to do the arg copying from/to userspace. Right now the v4l2 ioctl > translation functions calls v4l2_driver->ioctl(), which is expected to > receive a kernel pointer. With file_operations->ioctl() this obviously I speciically didnt do this with v4l1 because of driver private ioctls which you cannot move into kernel space. The networking code takes a different tack and has a seperate pointer for device private ioctl handling > We can't get rid of the minor numbers (yet?). devfs is optional and > still marked experimental, so it must work with the traditional > major/minor scheme too. You need major/minor numbers for ever. You can swap them for text strings and break compatibility massively but it doesnt change anything in truth. > vbi_format) in v4l1 and VIDIOC_G_FMT(struct v4l2_format) with > type = V4L2_TYPE_VBI in v4l2. I can't see any difference here, > and these are the only vbi-specific ioctls in v4l1/2 ... Where they are the same keep the old one. Similarly you can map formats by making most of the numbers line up. Alan
