public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Risto Pajula <rippe.shacknet@gmail.com>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Nova-T-500 Remote & dvb-usb-dib0700-1.20.fw
Date: Sun, 12 Oct 2008 23:32:58 +0300	[thread overview]
Message-ID: <48F25EFA.1080105@gmail.com> (raw)

Hello.

I can confirm the problem reported in the email:
http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029625.html

I tested using the v4l-dvb mercurial from today and when 
dvb-usb-dib0700-1.20.fw is used the remote always repeats the last 
pressed key until the another key is pressed. If I use the same v4l-dvb 
drivers and the dvb-usb-dib0700-1.10.fw the remote works just fine. The 
cold boot is required between the tests to see any difference.

However I can not get any "dib0700: Unknown remote controller key:" but 
dtv_property_cache_sync() appears in few minutes in the dmesg.

My system is:
Suse 11.0 2.6.25.16-0.1-default x86_64

I looked at the code and by making a lot of assumptions.... ;) I guess 
the call to the dib0700_rc_setup() from the dib0700_rc_query() wont 
erase the last IR code from the chip anymore if the new firmware is 
used...? However I really don't have idea how to fix it.. I would be 
happy to test anything if you have some suggestions.

BR.
Risto Pajula

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

             reply	other threads:[~2008-10-12 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-12 20:32 Risto Pajula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-10 11:30 [linux-dvb] Nova-T-500 Remote & dvb-usb-dib0700-1.20.fw Public Email

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=48F25EFA.1080105@gmail.com \
    --to=rippe.shacknet@gmail.com \
    --cc=linux-dvb@linuxtv.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