By "not detected as v4l capable" I meant, that there is no device with "video4linux" capability in lshal, thats why I filed this bug against hal. Also, as far as I know, the /sys entry is not created by hal, so the fact that it exist does not mean hal has recognized the device correctly.
Maybe as a workaround a custom .fdi-file could be used, which creates such a device.
By "not detected as v4l capable" I meant, that there is no device with "video4linux" capability in lshal, thats why I filed this bug against hal. Also, as far as I know, the /sys entry is not created by hal, so the fact that it exist does not mean hal has recognized the device correctly.
Maybe as a workaround a custom .fdi-file could be used, which creates such a device.