From: Johannes Engel <jcnengel@googlemail.com>
To: Thierry Merle <thierry.merle@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: dvb-usb-cinergyT2
Date: Wed, 11 Feb 2009 23:50:53 +0100 [thread overview]
Message-ID: <4993564D.1060903@googlemail.com> (raw)
In-Reply-To: <49932E47.7050307@free.fr>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Thierry Merle wrote:
> another user has got the same problem, except that the led still lights up.
> Can you tell us what it the firmware version in your device?
> You can see it by doing lsusb -vvv, for the Cinergy T2 entry this is the "bcdDevice" line.
> I have the 1.06 firmware version and it works.
> Cheers,
> Thierry
>
Hi Thierry,
thanks for your message! I just tried again and miraculously enough it
seems to work now. In the meantime I only did a kernel upgrade to
2.6.28.4. So maybe that was the trick. :)
Nonetheless I attach the lsusb output for further reference, my firmware
version though seems to be the same as yours: 1.06.
Cheers, Johannes
[-- Attachment #2: lsusb.txt --]
[-- Type: text/plain, Size: 2784 bytes --]
Bus 005 Device 002: ID 0ccd:0038 TerraTec Electronic GmbH Cinergy T^2 DVB-T Receiver
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 0x0ccd TerraTec Electronic GmbH
idProduct 0x0038 Cinergy T^2 DVB-T Receiver
bcdDevice 1.06
iManufacturer 1 TerraTec GmbH
iProduct 2 Cinergy T²
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 476mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 3 Highspeed Bulk Transfer
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 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
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
prev parent reply other threads:[~2009-02-11 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 19:03 dvb-usb-cinergyT2 Johannes Engel
2009-02-11 20:00 ` dvb-usb-cinergyT2 Thierry Merle
2009-02-11 22:50 ` Johannes Engel [this message]
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=4993564D.1060903@googlemail.com \
--to=jcnengel@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=thierry.merle@free.fr \
/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