From: Alexander List <alex@list.priv.at>
To: linux-media@vger.kernel.org
Subject: DMB-H USB Sticks: MagicPro ProHDTV Mini 2 USB
Date: Fri, 15 Feb 2013 09:23:05 +0800 [thread overview]
Message-ID: <511D8DF9.7060508@list.priv.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]
Hi,
frustrated that I couldn't watch the Chinese New Years' Fireworks on TVB
Jade using my RTL2832U based DVB-T stick in Hong Kong, I just bought a
MagicPro ProHDTV Mini 2
USB stick. Given that HK is now part of China (somehow), they decided to
follow the mainland DTV standard, so it's DTMB (DMB-T/H) over here.
The package says it only supports Windows, but I never believe the
packaging, and I believe in Linux hackers :)
lsusb -v says:
Bus 001 Device 008: ID 1b80:d39f Afatech
This looks *very* similar to the RTL2832U, in fact dmesg says it's a
Realtek chip:
[58773.739843] usb 1-1.1: new high-speed USB device number 8 using ehci_hcd
[58773.835657] usb 1-1.1: New USB device found, idVendor=1b80,
idProduct=d39f
[58773.835665] usb 1-1.1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
[58773.835670] usb 1-1.1: Product: usbtv
[58773.835673] usb 1-1.1: Manufacturer: realtek
Full lsusb -v output is attached.
I checked here but it's not listed, but other (PCIe) devices from the
same manufacturer are:
http://linuxtv.org/wiki/index.php/DMB-T/H_PCIe_Cards
I'm more than willing to get this thing supported under Linux - just let
me know what I can do to help.
I have
a) the stick
b) the Windows driver/software CD (soon as an ISO)
What I can provide is
a) help getting more info on the hardware (taking it apart etc.)
b) provide remote access to a box with the stick plugged in if necessary
c) test new code / patches
Cheers
Alex
[-- Attachment #2: lsusb.txt --]
[-- Type: text/plain, Size: 2309 bytes --]
Bus 001 Device 008: ID 1b80:d39f Afatech
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x1b80 Afatech
idProduct 0xd39f
bcdDevice 1.00
iManufacturer 1
iProduct 2
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 5
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
next reply other threads:[~2013-02-15 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 1:23 Alexander List [this message]
2013-02-15 9:38 ` DMB-H USB Sticks: MagicPro ProHDTV Mini 2 USB Antti Palosaari
[not found] ` <511E16FF.4050602@list.priv.at>
2013-02-15 11:38 ` Antti Palosaari
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=511D8DF9.7060508@list.priv.at \
--to=alex@list.priv.at \
--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).