Em28xx devices
Jump to navigation
Jump to search
This article discusses some USB interface chipset families produced by EMPIA, and, in addition, addresses the driver that support these chips.
How to compile the latest em28xx driver?
- Start your computer without (not plugged) em28xx device
- Download v4l-dvb tree
shell> hg clone http://linuxtv.org/hg/v4l-dvb
- Compile
shell> cd v4l-dvb shell> make shell> make install
- Now plug your device and start your favorite application
Firmware
Information
How to get it?
Error: unable to open firmware v4l-cx25840.fw
Manually Extracting and Installing the Firmware
cd /tmp shell> wget --user=wtv --password=Support07! ftp://ftp.hauppauge.com/Support/PVR150/Beta/070206%20amity2%202.0.48.25037.prerelease.zip shell> unzip "070206 amity2 2.0.48.25037.prerelease.zip" shell> cp HcwMakoC.ROM /lib/firmware/v4l-cx25840.fw
Based on ivtv firmware wiki
Error: firmware xc3028-v27.fw not found
firmware: requesting xc3028-v27.fw xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
Boards
How to identify my USB vendor/product id?
shell> lsusb
If you can't recognize the vendor/product id from your device contact linux-media mail-list
Validated boards
What's it?
We use this term to advise that boards were tested by user or developer.
Table of validated boards
| Define | Name | Vendor/Product ID | Supported modes |
|---|---|---|---|
Not Validated boards
What's it?
Not validate means: that your device was added to kernel but the developer(es) doesn't have the hardware for tests. If you would like to help and inform that you hardware work (or not) please see section How to validate my vendor/product id at upstream kernel
Table of NOT validated boards
| Define | Name | Vendor/Product ID | Status |
|---|---|---|---|
How to validate my vendor/product id at upstream kernel?
- Send your board name, lsusb output and tests made to linux-media mail-list
- Example:
From: foobar To: linux-media@... Subject: em28xx: new board id [0b1a:2821]
Hi,
I've made tests with my Pixelview board:
Model: Prolink PlayTV USB 2.0 Vendor/Product id: [0b1a:2821].
Tests made:
- Analog [Worked] - DVB [this board doesn't support dvb mode]
Tested-by: foobar <foobar@foobar.com>
~foobar
Otherwise, if you had any issue, please contact linux-media mail-list.
If some features doesn't work (i.e: audio, dvb, s-video)
Should I call whom?
Please contact linux-media mail-list.
Usbsnoop
If you were asked to sniff your device, use this instructions
About em28xx models
em2800/em2820/em2821/em2840
- used on older analog only device designs. These chips have support for USB Audio Class; so, audio module is snd-usb-audio
em2820/em2840 based devices
- ADS Tech Instant TV (USBAV-704)
- Gadmei utv 310
- Pinnacle_PCTV_USB2
- USBGear USB2.0 Video Adapter With Audio (VD204)
- V-Gear PocketTV
em2860
em2860 based devices
em2870/2871/2872/2873
- supports DVB/ATSC (but with no analog support). This is targeted at digital only devices.
em2874
- next generation version of the em2870 design - they moved around a bunch of registers compared to em2870/2880 and the chip itself supports two transport streams (although most designs will probably only use one stream).
em2880/2881/2883
- supports DVB/ATSC. Doesn't provide USB Audio Class. Instead, digital audio is provided via an USB Vendor Class; so, these chips require the em28xx-alsa module for digital audio to work.
em2880 based devices
- EVGA inDtube
- KWorld 350U DVB-T
- KWorld DVB-T 355U
- KWorld 310U
- KWorld USB2800
- Pinnacle PCTV unidentified DVB-T USB device
- Videology 20K14XUSB webcam
em2710/em2750 based devices
- used by on some Webcams.
Some Misc stuff
The following needs to be cleaned up and/or integrated into the article:
Feature Support
- No firmware is required for em28xx ICs ... note: though em28xx based devices paired with some tuners will need firmware for the tuner (i.e. there are em28xx based devices paired with a XCeive XC3028 or XC2028 tuner, which require a generic firmware from Xceive).
About Driver
- Development -- originally by 4 Ludovico Cavedon, Markus Rechberger, Mauro Carvalho Chehab, Sascha Sommer.
- One of the authors, Markus Rechberger, is now developing only closed source binary drivers.
External Links
Additional Help
Contact developers at linux-media mail-list