From: Norret Thierry <tnorret@yahoo.com>
To: linux-media@vger.kernel.org
Subject: Re: HVR-4000 may be broken in kernel mods (again) ?
Date: Sat, 12 Nov 2011 14:10:15 +0000 (UTC) [thread overview]
Message-ID: <loom.20111112T150258-917@post.gmane.org> (raw)
In-Reply-To: CAGoCfiwnOTv=yhFeAsjQ+=5vrsUfy5b8HqtXGiFuimXe2M-+Bw@mail.gmail.com
Devin Heitmueller <dheitmueller <at> kernellabs.com> writes:
>
> On Sat, Nov 12, 2011 at 8:14 AM, Lars Schotte <gusto <at> guttok.net> wrote:
> > i am alos curious what he means by "try to use it". i mean did he try
> > to use it with tzap, or szap, or w_scan, or what? because i dont even
> > know about mythtv, i only use dvbutils, mplayer, xine and vdr.
>
> I agree with Lars on this. It would be useful if the user could
> describe in more detail his testing methodology. Also, is there some
> previous kernel in which he knew it was working properly? Has he
> *ever* seen it work in his environment? Do we know definitively that
> this really a regression or has the user never seen the board work?
>
> Devin
>
I think your problem and mine are the same
I've too an hauppauge dvb-t
http://www.spinics.net/lists/linux-media/msg39917.html
Since upgrade from kernel 2.6.38 to 2.6.39/3.0 channels can't be lock.
next prev parent reply other threads:[~2011-11-12 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 10:33 HVR-4000 may be broken in kernel mods (again) ? jonathanjstevens
2011-11-12 12:55 ` Devin Heitmueller
2011-11-12 13:14 ` Lars Schotte
2011-11-12 13:20 ` Devin Heitmueller
2011-11-12 14:10 ` Norret Thierry [this message]
2011-11-12 14:16 ` jonathanjstevens
2011-11-12 14:53 ` jonathanjstevens
2011-11-12 15:06 ` Patrick Dickey
2011-11-12 16:37 ` jonathanjstevens
2011-11-12 15:08 ` Devin Heitmueller
[not found] ` <CAA7M+FCG4Q5Xyu45rnQs9qecHOWRm4sw9bYvoe6neu44E6=xZg@mail.gmail.com>
2011-11-12 16:44 ` Fwd: " jonathanjstevens
2011-11-13 15:37 ` James
2011-11-13 16:16 ` jonathanjstevens
2011-11-14 18:29 ` jonathanjstevens
2011-11-14 18:32 ` jonathanjstevens
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=loom.20111112T150258-917@post.gmane.org \
--to=tnorret@yahoo.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