From: Ronald Tallent <ron@tallent.ws>
To: linux-media@vger.kernel.org
Subject: 3rd posting: em28xx: new board id [1f4d:1abe]
Date: Sun, 06 Sep 2015 14:16:48 -0500 [thread overview]
Message-ID: <1441567008.5526.8.camel@Amy> (raw)
Hi,
This is my third attempt to post this information to mailing list in a
little over a week. Am I invisible? Can nobody see my messages? I have
precisely followed the instructions posted on
linuxtv.org/wiki/index.php/Em28xx_devices#How_to_validate_my_vendor.2Fproduct_id_at_upstream_kernel.3F
trying to get my hardware validated. What else do I need to do? Can
someone answer please and help me.
Thanks,
--Ronald
I've tested my USB easycap device (Geniatech iGrabber) in Ubuntu
14.04.
Make: Geniatech
Model: iGrabber for MAC
Vendor/Product ID: [1f4d:1abe]
Product website: www.geniatech.com/pa/igrabber.asp
Tests Made:
- Audio Capture [worked]
- Video Capture [device not detected]
- DVB [does not have DVB]
Tested by:
ron@tallent.ws
Detailed information on device and system below for reference:
uname -a:
3.13.0-62-generic #102-Ubuntu SMP Tue Aug 11 14:29:36 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
dmesg:
[] usb 3-3.3: new high-speed USB device number 8 using xhci_hcd
[] usb 3-3.3: New USB device found, idVendor=1f4d, idProduct=1abe
[] usb 3-3.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[] usb 3-3.3: Product: USB Device
[] usbcore: registered new interface driver snd-usb-audio
lsusb:
Bus 003 Device 008: ID 1f4d:1abe G-Tek Electronics Group
Hardware:
Opened the case and found the following text printed on the board:
HandyCap
v1.51
2007-4-24
Three chips on board are:
1: empia
EM2860
P8367-010
201036-01AG
2: Trident
SAA7113H
C2P409.00 02
A5G11152
3: eMPIA
Technology
EMP202
UT11958
1027
next reply other threads:[~2015-09-06 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 19:16 Ronald Tallent [this message]
2015-09-06 19:53 ` 3rd posting: em28xx: new board id [1f4d:1abe] Mauro Carvalho Chehab
2015-09-06 23:58 ` Call for help: " Ronald Tallent
2015-09-07 11:57 ` Mauro Carvalho Chehab
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=1441567008.5526.8.camel@Amy \
--to=ron@tallent.ws \
--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;
as well as URLs for NNTP newsgroup(s).