2.6.30: missing audio device in bttv

2009-06-11 Thread Udo A. Steinberg
Hi all, With Linux 2.6.30 the BTTV driver for my WinTV card claims bttv0: audio absent, no audio device found! and audio does not work. This worked up to and including 2.6.29. Is this a known issue? Does anyone have a fix or a patch for me to try? Cheers, - Udo Output for 2.6

Re: [v4l-dvb-maintainer] 2.6.30: missing audio device in bttv

2009-06-11 Thread Udo A. Steinberg
On Thu, 11 Jun 2009 22:18:10 +0200 Hans Verkuil (HV) wrote: HV> On Thursday 11 June 2009 22:14:02 Udo A. Steinberg wrote: HV> > Hi all, HV> > HV> > With Linux 2.6.30 the BTTV driver for my WinTV card claims HV> > HV> > bttv0: audio absent, no audio device f

Re: [v4l-dvb-maintainer] 2.6.30: missing audio device in bttv

2009-06-11 Thread Udo A. Steinberg
On Thu, 11 Jun 2009 23:46:48 +0200 Hans Verkuil (HV) wrote: HV> Hmm, my patch needs a bit more work. But to get your setup working try to HV> revert the change you made and do just this: HV> HV> Go to drivers/media/video/Makefile and move this line: HV> HV> obj-$(CONFIG_VIDEO_MSP3400) += msp3400

Re: [v4l-dvb-maintainer] 2.6.30: missing audio device in bttv

2009-06-11 Thread Udo A. Steinberg
On Fri, 12 Jun 2009 01:01:59 +0200 Hans Verkuil (HV) wrote: HV> I've fixed the problem in my original patch. I've attached the new HV> version. It works fine with ivtv, the problems with reading the eeprom HV> are now fixed. Please test and if it still doesn't work then I'll have HV> to install my

Hauppauge/IR breakage with 2.6.28/2.6.29

2009-03-25 Thread Udo A. Steinberg
Hi, The following patch http://kerneltrap.org/mailarchive/git-commits-head/2008/10/13/3643574 that was added between 2.6.27 and 2.6.28 has resulted in my Hauppauge WinTV IR remote not working anymore. I've tracked down the breakage to: if (dev!=0x1e && dev!=0x1f) return 0; in drivers/media/vi

Re: Hauppauge/IR breakage with 2.6.28/2.6.29

2009-03-25 Thread Udo A. Steinberg
On Thu, 26 Mar 2009 00:26:47 + Darron Broad (DB) wrote: DB> It's something I forget to deal with in that patch. A solution DB> would be to allow a device address to be a module param to DB> override the more modern addresses of 0x1e and 0x1f. DB> DB> I can't remember addresses off the top of

[PATCH] Allow the user to restrict the RC5 address

2009-03-25 Thread Udo A. Steinberg
Mauro, This patch allows users with multiple remotes to specify an RC5 address for a remote from which key codes will be accepted. If no address is specified, the default value of 0 accepts key codes from any remote. This replaces the current hard-coded address checks, which are too restrictive.

Re: [PATCH] Allow the user to restrict the RC5 address

2009-03-26 Thread Udo A. Steinberg
On Thu, 26 Mar 2009 12:45:18 -0400 Steven Toth (ST) wrote: ST> I too tend to have multiple remotes, I don't think it's that unusual for ST> long standing Hauppauge customers to have many boards with many types of ST> remotes. ST> ST> > It might be better to have an option to explicitly allow old