Hi all, While looking at the video_register_device changes that broke ov511 I realized that the video_register_device_index function is never called from drivers. It will always assign a default index number. I also don't see a good use-case for giving it an explicit index. My proposal is to remove this API. Since it is never called, nothing will change effectively. I'm never happy with unused functions. However, I think we do need a new video_register_device_range function. This would be identical to video_register_device, but with an additional count argument: this allows drivers to select a kernel number in the range of nr to nr + count - 1. If cnt == -1, then the maximum is the compiled-in maximum. So video_register_device would call video_register_device_range(...nr, 1), thus restoring the original behavior, while ivtv and cx18 can call video_register_device_range(...nr, -1), thus keeping the current behavior. Comments? Regards, Hans -- Hans Verkuil - video4linux developer - sponsored by TANDBERG Telecom -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
