All of lore.kernel.org
 help / color / mirror / Atom feed
From: Emanoil Kotsev <emanoil.kotsev@sicherundsicher.at>
To: V4L Mailing List <linux-media@vger.kernel.org>
Subject: Terratec T USB XXS 0ccd:00ab device
Date: Sun, 13 Sep 2009 14:56:56 +0200	[thread overview]
Message-ID: <200909131457.05286.emanoil.kotsev@sicherundsicher.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 1920 bytes --]

Hello, I've just subscribed this list. I'm normally using knode to read news, 
but somehow I can not pull the groups etc from the vger server.

I also tried to post to linux-dvb mailing list, but found out that it moved 
here. If you think I need to know something explicitly about participating to 
the list, please let me know.

The issue I'm facing is that my old TV card (HVR900) stopped working, so I 
googled around and decided to buy Terratec T USB XXS, reading it was 
supported in dvb_usb_dib0700

However after installing the card (usb-stick) it was not recognized (my one 
has product id 0x00ab and not 0x0078), so I googled again and found a hint to 
change the device id in dvb_usb_ids.h which was working for other Terratec 
card.

I pulled the latest v4l-dvb code and did it (perhaps I could have done it in 
the kernel 2.6.31), compiled, installed and it started working.

However I can not handle udev to get the remote control links created 
correctly. Can someone help me with it? How can I provide useful output to 
developers to solve the issues with ir? I read and saw that ir control keys 
are coded in the driver, so if the ir part of the 0x00ab card is different, 
how can I get a useful information that can be coded for this card? Who is 
doing the work at linux-dvb?

I read there are other people, returning the cards to the seller, because it's 
not working/supported by linux, which does not seem to be really true.

Luckilly I have a bit kernel experience and good C knowledge and could do 
testing if somebody can have a look at the issues - the code is completely 
new to me so that I prefer to be an alpha tester for the device.

thanks for patience in advance and kind regards


-- 
pub   1024D/648C084C 2008-06-06 Emanoil Kotsev 
<emanoil.kotsev@sicherundsicher.at>
 Primary key fingerprint: 002C AF99 232A 5A44 EF9E  6D7D 0D65 4160 648C 084C

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-09-13 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-13 12:56 Emanoil Kotsev [this message]
2009-09-13 13:41 ` Terratec T USB XXS 0ccd:00ab device Mauro Carvalho Chehab
2009-09-14 21:29 ` Emanoil Kotsev

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=200909131457.05286.emanoil.kotsev@sicherundsicher.at \
    --to=emanoil.kotsev@sicherundsicher.at \
    --cc=emanoil.kotsev@sicherundsicher.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.