public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "petercarm" <linuxtv@hotair.fastmail.co.uk>
To: "linux-dvb" <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] dib0700 remote control support fixed
Date: Mon, 01 Dec 2008 20:03:48 +0000	[thread overview]
Message-ID: <1228161828.28118.1287661397@webmail.messagingengine.com> (raw)

On Mon, 1 Dec 2008 13:54:19 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> Hello Peter,
> 
> Of the devices that you have, which are the ones that are failing?
> Both of the dibcom devices?
> 
> I am not familiar with how lirc interacts with the dib0700 driver,
> since the driver polls the bulk endpoint every 50ms and injects the
> keys directly.  I will have to look at the driver and see how this
> hooks into lirc.
> 
> I suspect that most people are not using lirc at all, since the device
> works without it.  This would explain why you are the only person I
> know of still reporting these problems.
> 
> Could you please send my your lirc configuration so I can attempt to
> reproduce the issue locally?  If I can get an environment that
> reproduces the issue, I can almost certainly fix it.
> 
> Thanks,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller

The Nova-T 500 and the Nova TD USB stick are the two dibcom devices.

What output should I be getting from the remote control?  Having
previously seen RC signals coming through on /dev/input I need some
clues for where to look if things have changed.

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

             reply	other threads:[~2008-12-01 20:03 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 20:03 petercarm [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-20 15:14 [linux-dvb] dib0700 remote control support fixed Devin Heitmueller
2008-11-20 20:39 ` petercarm
2008-11-20 20:46   ` Devin Heitmueller
2008-11-21  0:40     ` petercarm
2008-11-21  1:02       ` Devin Heitmueller
2008-12-01  4:59       ` Devin Heitmueller
2008-12-01 17:31         ` petercarm
2008-12-01 18:54           ` Devin Heitmueller
2008-12-01 20:13             ` petercarm
2008-12-01 20:35               ` Devin Heitmueller
2008-12-01 20:40               ` petercarm
2008-12-01 20:47                 ` Devin Heitmueller
2008-12-01 21:15                   ` petercarm
2008-12-02 14:35                 ` Darren Salt
2008-12-02 17:39                   ` petercarm
2008-12-02 21:49                     ` petercarm
2008-12-02 22:13                       ` Devin Heitmueller
2008-12-03 15:30                         ` petercarm
2008-12-03 15:34                           ` Devin Heitmueller
2008-12-03 16:27                             ` petercarm
2008-12-03 16:35                               ` Devin Heitmueller
2008-12-01 20:17           ` Robert Watkins

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=1228161828.28118.1287661397@webmail.messagingengine.com \
    --to=linuxtv@hotair.fastmail.co.uk \
    --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