2013 08:08
Betreff: Fwd: Strange USB transfer problems with Delock 61959
An:
Cc:
> Hello linux media developers,
>
> I have recently bought a Delock 61959 DVB-C USB stick. It's working
> fine under Windows. All SD and HD channels can be found and watched
> fine. But under Linux, I
Hello linux media developers,
I have recently bought a Delock 61959 DVB-C USB stick. It's working
fine under Windows. All SD and HD channels can be found and watched
fine. But under Linux, I get a really strange behaviour. If I connect
the stick to a USB 3.0 port, it is somehow workin
On 04/13/2013 06:03 PM, Jakob Haufe wrote:
Hardware is the same as MaxMedia UB425-TC but ships with a different
remote.
Signed-off-by: Jakob Haufe
Reviewed-by: Antti Palosaari
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a
On 04/13/2013 06:03 PM, Jakob Haufe wrote:
This adds the keytable for the remote that comes with the Delock 61959.
NEC protocol with address 0x866b.
Signed-off-by: Jakob Haufe
Reviewed-by: Antti Palosaari
--
http://palosaari.fi/
--
To unsubscribe from this list: send the line
On 04/13/2013 06:03 PM, Jakob Haufe wrote:
This time for real with all bells and whistles:
Delock 61959 is a relabeled MexMedia UB-425TC with a different USB ID and a
different remote.
Patch 1 adds the keytable for the remote control and patch 2 adds support for
the device itself. I'm re
hauppauge_930c_digital[] = {
#endif
/* 1b80:e425 MaxMedia UB425-TC
+ * 1b80:e1cc Delock 61959
* GPIO_6 - demod reset, 0=active
* GPIO_7 - LED, 0=active
*/
@@ -2016,6 +2017,19 @@ struct em28xx_board em28xx_boards[] = {
.i2c_speed= EM28XX_I2C_CLK_WAIT_ENABLE
This adds the keytable for the remote that comes with the Delock 61959.
NEC protocol with address 0x866b.
Signed-off-by: Jakob Haufe
---
drivers/media/rc/keymaps/Makefile |1 +
drivers/media/rc/keymaps/rc-delock-61959.c | 83
include/media/rc-map.h
This time for real with all bells and whistles:
Delock 61959 is a relabeled MexMedia UB-425TC with a different USB ID and a
different remote.
Patch 1 adds the keytable for the remote control and patch 2 adds support for
the device itself. I'm reusing maxmedia_ub425_tc as I didn'
,6 +2173,8 @@ struct usb_device_id em28xx_id_table[] = {
.driver_info = EM2860_BOARD_EASYCAP },
{ USB_DEVICE(0x1b80, 0xe425),
.driver_info = EM2874_BOARD_MAXMEDIA_UB425_TC },
+ { USB_DEVICE(0x1b80, 0xe1cc), /* De
On 04/12/2013 05:17 PM, Jakob Haufe wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 9 Apr 2013 14:48:05 +0200
Jakob Haufe wrote:
Will do so tonight and report back.
Took a little longer but it worked as expected. Patch follows in a separate
mail.
dmesg output:
[19.474818] em2
On 04/12/2013 05:18 PM, Jakob Haufe wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Delock 61959 seems to be a relabeled version of Maxmedia UB425-TC with a
different USB ID. PCB is marked as "UB425-TC Ver: A" and this change
makes it work without any obvious problems.
Sig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Delock 61959 seems to be a relabeled version of Maxmedia UB425-TC with a
different USB ID. PCB is marked as "UB425-TC Ver: A" and this change
makes it work without any obvious problems.
Signed-off-by: Jakob Haufe
- ---
drivers/media/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 9 Apr 2013 14:48:05 +0200
Jakob Haufe wrote:
> Will do so tonight and report back.
Took a little longer but it worked as expected. Patch follows in a separate
mail.
dmesg output:
[19.474818] em28xx: New device USB 2875 Device @ 480 Mbps (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 24 Mar 2013 15:10:54 +0200
Antti Palosaari wrote:
> Maybe it is em28xx + DRX-K + tda18271 based. There is few such devices
> already supported by em28xx driver. First device to test is 1b80:e425
> MaxMedia UB425-TC.
Perfect guess! I just g
Maybe it is em28xx + DRX-K + tda18271 based. There is few such devices
already supported by em28xx driver. First device to test is 1b80:e425
MaxMedia UB425-TC. Just replace USB ID 0xe425 with 0xe1cc, compile and
test. There is some other devices too, especially all those which are
using drx-k.
Hi there,
today i got a new DVB-T / DVB-C USB Stick but as far as i can see on
the web it is not (yet) supported.
Is this currently being worked on or is there something i can do to
get it working?
Here is the lsusb output:
Device Descriptor:
bLength18
bDescriptorType
16 matches
Mail list logo