public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: <jean.bruenn@ip-minds.de>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Jean Delvare <khali@linux-fr.org>
Subject: Re: WinTV 1400 broken with recent versions?
Date: Sat, 12 Mar 2011 00:04:10 +0100	[thread overview]
Message-ID: <af7d57a1bb478c0edac4cd7afdfd6f41@localhost> (raw)
In-Reply-To: <81E0AF02-0837-4DF8-BFEA-94A654FFF471@wilsonet.com>


Hey,

i tried to revert that patch manually (e.g. switching into the directory,
vim cx23885-i2c.c, removing the stuff which was added), then "make clean"
"make distclean" followed by "./build.sh" then make rmmod, then plugged in
the card, dmesg shows it loaded the card correctly, all fine, then i did
./scan Scanlist.txt and i get the same i2c related errors. Did a reboot
just to verify, still getting those, scan gives no results always "tuning
failed". 

Then i reverted another patch (just to make sure..
http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-2.6.git;a=commit;h=f4acb3c4ccca74f5448354308f917e87ce83505a)
- However, this didn't help. So, the problem might be somewhere else. 

I did some more research and it seems i'm not the only one with those
issues, tho nearly none gets answers regarding this trouble, e.g.:

(same card - also expresscard, december 2010)
http://www.spinics.net/lists/linux-media/msg27042.html
(not the same card, tho similar error, hvr 1500, i got hvr 1400 - februar
2009)
http://www.linuxtv.org/pipermail/linux-dvb/2009-February/031839.html

I'm running out of ideas where the problem might be located. i also tried
to switch the firmware by extracting the firmware manually, didn't help.
There's a low power version and another one available, tried to replace,
didn't work neither.

So it seems, this driver is broken at least since december 2010. Totally
weird why there's such a mess, i know for sure that this WAS working.

Anyone, any idea? Maybe something wrong configured in kernel? Might
running native 64bit the cause (no multilib/32bit compat libs here)?

> I knew this all seemed too familiar... :)
> 
>
http://git.kernel.org/?p=linux/kernel/git/mchehab/linux-2.6.git;a=commit;h=67914b5c400d6c213f9e56d7547a2038ab5c06f4
> 
> Its already being reverted for 2.6.38 final (hopefully -- Mauro included
> that in the pull req sent to Linus today).

  reply	other threads:[~2011-03-11 23:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-09 16:52 WinTV 1400 broken with recent versions? Jean-Michel Bruenn
2011-03-09 15:55 ` Jarod Wilson
2011-03-10  0:00   ` jean.bruenn
2011-03-10 14:37     ` Jarod Wilson
2011-03-10 20:45       ` Jarod Wilson
2011-03-11 23:04         ` jean.bruenn [this message]
2011-03-11 23:21           ` Devin Heitmueller
2011-03-11 23:30             ` jean.bruenn
2011-03-11 23:35               ` Devin Heitmueller
2011-03-12 13:59                 ` Jarod Wilson
2011-03-13  2:22                   ` Jean-Michel Bruenn
2011-03-13  1:45                     ` Devin Heitmueller
2011-03-13 12:04                       ` Jean-Michel Bruenn
2011-04-20  6:09                         ` Ryan
2011-04-20  9:42                           ` Jean-Michel Bruenn
  -- strict thread matches above, loose matches on Subject: below --
2011-06-19 10:13 Jean-Michel Bruenn
2011-03-09 16:38 Jean-Michel Bruenn

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=af7d57a1bb478c0edac4cd7afdfd6f41@localhost \
    --to=jean.bruenn@ip-minds.de \
    --cc=jarod@wilsonet.com \
    --cc=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.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