Skip to contentSkip to conversation

Macro Silicon M2106

V4l2-library Hans Verkuil 2 participants 2 messages Feb 29, 2020 2 messages not in the archive Media (V4L/DVB)

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw

Hi Gert,

(changed the mailinglist to linux-media since this topic is not related to libv4l2 and CCed Laurent who might know more about this)

Quoted 7 lines · On 2/29/20 10:06 AM, [email protected] wrote:

Hello,

About a year ago a page about a new Easycap variant was added to the wiki -
https://linuxtv.org/wiki/index.php/Talk:Easycap
Has anybody been working on this? I just bought a video grabber - and it seems to be one of those...

Sold as BASETech BR116, but lsusb lists it as ID 534d:0021 MACROSILICON AV TO USB2.0

No, to my knowledge nobody is working on this.

It's not clear from the wiki what exactly is wrong, Laurent might have some insight in that.

Regards,

Hans

Quoted 9 lines

Thanks,

_______________________________________________
V4L2-library mailing list
[email protected]
https://www.linuxtv.org/cgi-bin/mailman/listinfo/v4l2-library

#3 lore raw

Hi Gert,

Quoted 10 lines · Hans Verkuil

(changed the mailinglist to linux-media since this topic is not related to libv4l2 and CCed Laurent who might know more about this)

Quoted 6 lines · On 2/29/20 10:06 AM, [email protected] wrote:

Hello,

About a year ago a page about a new Easycap variant was added to the wiki -
https://linuxtv.org/wiki/index.php/Talk:Easycap
Has anybody been working on this? I just bought a video grabber - and it seems to be one of those...

Quoted 6 lines
Quoted 1 line

Sold as BASETech BR116, but lsusb lists it as ID 534d:0021 MACROSILICON AV TO USB2.0

No, to my knowledge nobody is working on this.

It's not clear from the wiki what exactly is wrong, Laurent might have some insight in that.

The first error reported by the driver is

[47452.103222] uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling workaround.

It is quite common for UVC devices not to support GET_DEF on the PROBE control (I assume because the Windows driver doesn't use that request), so the uvcvide driver falls back to a different method automatically. However, in some less common cases, invalid requests can actually crash the device firmware. Let's thus first check if enabling the workaround without trying the unsupported request helps. This is done by setting the UVC_QUIRK_PROBE_DEF quirk (0x100). Could you

- Unload the uvcvideo driver (rmmod uvcvideo)
- Reload the driver with the quirk (modprobe uvcvideo quirks=0x100)

and see if it fixes your issue ?

Could you also please send me the output of

lsusb -d -v 534d:0021

running as root if possible ?

Signature · 3 lines
Regards,

Laurent Pinchart