public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: "Roman v. Gemmeren" <roman@hasnoname.de>
Cc: linux-media@vger.kernel.org
Subject: Re: MSI Digivox Micro HD support?
Date: Tue, 15 Sep 2009 22:52:33 +0300	[thread overview]
Message-ID: <4AAFF081.7000904@iki.fi> (raw)
In-Reply-To: <200909152050.32487.roman@hasnoname.de>

On 09/15/2009 09:50 PM, Roman v. Gemmeren wrote:
>>> 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

Bad new. This looks like totally new chip. In my understanding no-one is 
working for that and this is first time I hear even it.
http://www.abilis.com/

If they are willing to give specs and sample code for the GPL then 
someone could be willing to write driver. Or reverse-engineering...

Antti
-- 
http://palosaari.fi/

  reply	other threads:[~2009-09-15 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15 18:50 MSI Digivox Micro HD support? Roman v. Gemmeren
2009-09-15 19:52 ` Antti Palosaari [this message]
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=4AAFF081.7000904@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=roman@hasnoname.de \
    /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