public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Pickworth <ian@pickworth.me.uk>
To: Gert Vervoort <gert.vervoort@hccnet.nl>
Cc: video4linux-list@redhat.com
Subject: Re: Hauppauge WinTV regreession from 2.6.24 to 2.6.25
Date: Sun, 20 Apr 2008 13:26:27 +0100	[thread overview]
Message-ID: <480B3673.3040707@pickworth.me.uk> (raw)
In-Reply-To: <480B26FC.50204@hccnet.nl>

Gert Vervoort wrote:
> Ian Pickworth wrote:
>> I am testing a kernel upgrade from 2.6.24.to 2.6.25, and the drivers 
>> for   the Hauppauge WinTV appear to have suffered some regression 
>> between the two kernel versions.
>>
>> The problem is that the tuner is not being detected and set correctly 
>> for either the video or the radio device on the card.
>>
> Similar issue here with a Leadtek Winfast 2000XP card. Video works, but 
> radio doesn't.
> For my card I can workaround the issue by adding the "tuner=38" option 
> to the cx88xx module.
> 
>   Gert

That workaround works for me as well - with "tuner=38" for cx88xx I can 
now tune to both video and radio channels.

So it looks like its just the auto detection that has regressed in 2.6.25.

Thanks
Regards
Ian


--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2008-04-20 12:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-19 20:57 Hauppauge WinTV regreession from 2.6.24 to 2.6.25 Ian Pickworth
2008-04-20  0:47 ` hermann pitton
2008-04-20  9:15   ` Ian Pickworth
2008-04-20 11:20 ` Gert Vervoort
2008-04-20 12:26   ` Ian Pickworth [this message]
2008-04-20 13:06     ` hermann pitton
2008-04-20 16:18       ` Gert Vervoort
2008-04-20 21:16         ` hermann pitton
2008-04-24  3:55           ` hermann pitton
2008-04-25 13:56             ` Mauro Carvalho Chehab
2008-04-25 14:40               ` Michael Krufky
2008-04-25 14:45                 ` Mauro Carvalho Chehab
2008-04-25 15:06                   ` mkrufky
2008-04-25 21:48                     ` hermann pitton
2008-04-25 23:41                       ` hermann pitton
2008-04-26 11:59                     ` Mauro Carvalho Chehab
2008-04-26 12:58                       ` Ian Pickworth
2008-04-26 14:06                         ` Mauro Carvalho Chehab
2008-04-26 22:10                           ` hermann pitton
2008-04-26 23:19                             ` Mauro Carvalho Chehab
2008-04-27 20:15                               ` hermann pitton
2008-04-27 21:18                                 ` [linux-dvb] " Hartmut Hackmann
2008-04-28  1:01                                   ` hermann pitton
2008-04-28 14:21                                   ` Mauro Carvalho Chehab
2008-04-28 14:14                                 ` Mauro Carvalho Chehab
2008-04-25 15:03                 ` Mauro Carvalho Chehab
2008-04-25 16:55                   ` Gert Vervoort
2008-04-25 17:02                     ` Gert Vervoort
     [not found]                     ` <20080426090725.4a0fdcd4@gaivota>
2008-04-26 14:23                       ` Gert Vervoort
2008-04-26 15:38                         ` Mauro Carvalho Chehab
2008-04-26 16:59                           ` Gert Vervoort

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=480B3673.3040707@pickworth.me.uk \
    --to=ian@pickworth.me.uk \
    --cc=gert.vervoort@hccnet.nl \
    --cc=video4linux-list@redhat.com \
    /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