From: "Roman v. Gemmeren" <roman@hasnoname.de>
To: linux-media@vger.kernel.org
Subject: Re: MSI Digivox Micro HD support?
Date: Tue, 15 Sep 2009 20:50:32 +0200 [thread overview]
Message-ID: <200909152050.32487.roman@hasnoname.de> (raw)
Hi,
Am Tuesday 15 September 2009 20:31:29 schrieben Sie:
> On 09/15/2009 08:32 PM, Roman v. Gemmeren wrote:
> > hi list,
> >
> > i just bought the above mentioned DVBT-Stick after my terratec prodigy
> > died (from overheating i guess).
> > I remembered sth. about digivox being supported, but i found only drivers
> > for the "Digivox Mini II 3.0" which don't seem to recognize that stick at
> > all.
> >
> > Anyone got that card working? If it is just the usb-id which is missing,
> > how /where would i add that to the source?
>
> Just do lsusb -vvd USB:ID and post here. From that we usually can say
> which chips are used and correct driver needed for device. Also you can
> look driver .inf file, driver filenames, look strings from driver, look
> sniff or open the box to identify chips.
>
> Antti
This is the output for the Stick:
root@Seth:~strowi/tmp> lsusb -vvd 1ba6:0001
Bus 001 Device 005: ID 1ba6:0001
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x1ba6
idProduct 0x0001
bcdDevice 1.00
iManufacturer 1 Abilis Systems
iProduct 2 ATon2 DVB Receiver
iSerial 3 0001
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 300mA
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 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
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
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0000
(Bus Powered)
greetings,
Roman
next reply other threads:[~2009-09-15 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 18:50 Roman v. Gemmeren [this message]
2009-09-15 19:52 ` MSI Digivox Micro HD support? Antti Palosaari
2009-09-15 20:25 ` Roman v. Gemmeren
-- strict thread matches above, loose matches on Subject: below --
2009-09-15 17:32 Roman v. Gemmeren
2009-09-15 18:31 ` 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=200909152050.32487.roman@hasnoname.de \
--to=roman@hasnoname.de \
--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