OK so this is an upstream issue that the lack of support for V4L1 shouldn't trigger V4L support off all together (and/or the code needs to be reworked). I've punted this upstream.
OK so this is an upstream issue that the lack of support for V4L1 shouldn't trigger V4L support off all together (and/or the code needs to be reworked). I've punted this upstream.