gpt랑 대화하다가 검토중
uvc 카메라 두개를 하나의 root hub에 연결하면 대역폭 부족으로 하나가 인식이 안되는데
잘못된 보고를 하는 uvc 카메라의 경우(모든 장비가 bug-free가 아니니까 라고 표현)
이러한 것을 위해 드라이버 레벨에서 새롭게 대역폭을 계산해서 적용하도록 할 수 있는 옵션을 제공하나 보다.
다만 yuv 같은 경우처럼 고정된 크기라면 모를까 mjpeg 처럼 크기가 가변인건 안된다고 하는데
그럼.. h.264 cbr 의 경우는 ... 되는건가 싶었는데 압축 포맷이면 건너 뛴다고..
| if (!(format->flags & UVC_FMT_FLAG_COMPRESSED) && stream->dev->quirks & UVC_QUIRK_FIX_BANDWIDTH && stream->intf->num_altsetting > 1) { |
[링크 : https://github.com/torvalds/linux/blob/master/drivers/media/usb/uvc/uvc_video.c#L230]
나중에 한번 시도 할 만한 장비가 있으려나?
| sudo modprobe -r uvcvideo sudo modprobe uvcvideo quirks=0x80 |
| What are quirks and how do I use them? Not all UVC devices are bug-free. To be fair, most UVC devices are buggy, and some of them are so broken that they will not work with the uvcvideo driver out of the box. They should not have been labelled as UVC-compliant or even been sold, but the harm is done and we need to find a way to cope with it. That's why quirks have been introduced. When a quasi-UVC device exhibits a UVC non-compliance (either because its developers have interpreted the UVC specification incorrectly, or because they forgot to implement parts of the specification that are not used by the Windows driver), the uvcvideo driver needs to handle that device in a special way. The driver tries to do detect those cases automatically, but needs to be explictly instructed on some cases. Each of those special cases is called a quirk and is identified by a flag. UVC_QUIRK_FIX_BANDWIDTH 0x00000080 Try to estimate the bandwidth required for uncompressed streams instead on relying on the value reported by the camera. See FAQ 7 for more information. |
[링크 : https://ideasonboard.org/uvc/faq/]
'Linux API > usb' 카테고리의 다른 글
| usbfs / usb api (0) | 2012.02.04 |
|---|---|
| /proc/bus/usb 의 내용이 없을 경우(There is no files /proc/bus/usb) (0) | 2009.06.08 |
| usb 버스 정보 얻기 (0) | 2009.06.08 |
