From: Lutz <lutz@willerding.net>
To: linux-media@vger.kernel.org
Subject: UVC device not yet supported
Date: Thu, 23 Feb 2023 10:02:52 +0100 [thread overview]
Message-ID: <83f9ba3c-18bb-e0cd-e5ac-7c3281f2b5f8@willerding.net> (raw)
Hi,
just got a Endoskop camera from pearl, very cheap device (12,99€) and
connected it to a debian 11.
I'm trying to get a picture or stream from this camera, an came across
this page:
https://www.ideasonboard.org/uvc/
There is a section you'd like to be notified if a UVC device is not
listed there.
So this is my motivation to email you :)
Device is recogniced and listed in lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 008: ID 04cf:8819 Myson Century, Inc. USB 2.0 SD/MMC Reader
---> Bus 001 Device 009: ID 1908:2311 GEMBIRD Generic UVC 1.00 camera
[AppoTech AX2311] <---
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 004: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 007: ID 046d:c326 Logitech, Inc. Washable Keyboard K310
Bus 001 Device 005: ID 0557:8021 ATEN International Co., Ltd Hub
Bus 001 Device 003: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 002: ID 041e:4083 Creative Technology, Ltd Live! Cam
Socialize [VF0640]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
but no usable video device is created - at least i can not get a picture
from it.
The Creative Live! Cam does create a stream. I think this problem could
be solvable by some udev rules?
there is also a hw-probe for my machine:
https://linux-hardware.org/?probe=4f19f71811
tia for any hints
lutz willerding
next reply other threads:[~2023-02-23 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 9:02 Lutz [this message]
2023-02-23 10:54 ` UVC device not yet supported Ricardo Ribalda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83f9ba3c-18bb-e0cd-e5ac-7c3281f2b5f8@willerding.net \
--to=lutz@willerding.net \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox