From: <jean.bruenn@ip-minds.de>
To: Jarod Wilson <jarod@wilsonet.com>
Cc: <linux-media@vger.kernel.org>
Subject: Re: WinTV 1400 broken with recent versions?
Date: Thu, 10 Mar 2011 01:00:18 +0100 [thread overview]
Message-ID: <ba12e998349efa465be466a4d7f9d43f@localhost> (raw)
In-Reply-To: <76A39CFB-2838-4AD7-B353-49971F9F7DFF@wilsonet.com>
> This may already be fixed, just not in 2.6.37.x yet. Can you give
> 2.6.38-rc8 (or later) a try and/or the media_build bits?
Tried - Nope, same behaviour (same error messages in dmesg, no results by
scan)
>
http://linuxtv.org/wiki/index.php/How_to_Obtain,_Build_and_Install_V4L-DVB_Device_Drivers
I was unable to get that working; tried with 2.6.37.2 and 2.6.37.3 always
getting "invalid module format" and yeah, i tried with reboot, i tried
with a
fresh variant.. Also tried ./build.sh and make install and such stuff in
2.6.38-rc8, same.
next prev parent reply other threads:[~2011-03-10 0:00 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 [this message]
2011-03-10 14:37 ` Jarod Wilson
2011-03-10 20:45 ` Jarod Wilson
2011-03-11 23:04 ` jean.bruenn
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=ba12e998349efa465be466a4d7f9d43f@localhost \
--to=jean.bruenn@ip-minds.de \
--cc=jarod@wilsonet.com \
--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