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: Fri, 21 Nov 2008 00:40:30 +0000	[thread overview]
Message-ID: <1227228030.18353.1285952745@webmail.messagingengine.com> (raw)
In-Reply-To: <412bdbff0811201246x7df23a4ak2a6b29a06d67240@mail.gmail.com>

OK it is working on the Nova-T 500 but it is throwing up "Unknown remote
controller key" messages in dmesg in amongst correctly processing the
correct key presses.  I'll try using irrecord to work on a new
lircd.conf and see if it goes away.


On Thu, 20 Nov 2008 15:46:56 -0500, "Devin Heitmueller"
<devin.heitmueller@gmail.com> said:
> On Thu, Nov 20, 2008 at 3:39 PM, petercarm
> <linuxtv@hotair.fastmail.co.uk> wrote:
> > I'll do a test build in the next hour or so and confirm behaviour with:
> >
> > - a Hauppauge Nova-T 500 (PCI)
> > - a Hauppauge Nova-TD USB stick
> >
> > This will be my test gentoo system built from scratch with 2.6.25.
> > Everything apart from remote was working correctly until I pulled a
> > recent version down from mercurial.  My last build, based on Mercurial
> > from a few days ago has got my Nova-T 500 bitching away with i2c errors
> > if I stop of the lirc daemon.
> 
> The fix only went in on Sunday evening, so it's not surprising if you
> had the issue with a relatively recent build.
> 
> Please do report back regarding how your testing goes.  Note that you
> should not have any module options setup when you do the testing.
> 
> Thanks,
> 
> Devin
> 
> -- 
> Devin J. Heitmueller
> http://www.devinheitmueller.com
> AIM: devinheitmueller

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

  reply	other threads:[~2008-11-21  0:40 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2008-11-21  1:02       ` Devin Heitmueller
2008-11-22 12:54         ` [linux-dvb] Hauppauge Nova T 500, dvb-usb: error while enabling fifo Robert Watkins
2008-12-01  4:59       ` [linux-dvb] dib0700 remote control support fixed 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
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01 20:03 petercarm

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=1227228030.18353.1285952745@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