From: "José Suárez" <j.suarez.agapito@gmail.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Michael Krufky <mkrufky@linuxtv.org>,
"pasky@ucw.cz" <pasky@ucw.cz>, Linus Torvalds <torvalds@osdl.org>,
linux-dvb@linuxtv.org,
linux-kernel <linux-kernel@vger.kernel.org>,
v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>
Subject: Re: [linux-dvb] Avermedia 777 misbehaves after remote hack merged into v4l-dvb tree
Date: Tue, 14 Nov 2006 04:45:29 +0100 [thread overview]
Message-ID: <200611140445.30269.j.suarez.agapito@gmail.com> (raw)
In-Reply-To: <1163453015.26319.29.camel@201-2-70-92.bsace705.w.brasiltelecom.net.br>
El Lunes 13 Noviembre 2006 22:23, Mauro Carvalho Chehab escribió:
> Em Seg, 2006-11-13 às 16:09 -0500, Michael Krufky escreveu:
> > Linus Torvalds wrote:
> > > On Mon, 13 Nov 2006, Michael Krufky wrote:
> > >> Mauro -- that patch needs fixing / more testing before it goes to
> > >> mainstream...
> > >>
> > >> Could you please remove that changeset from your git tree before Linus
> > >> pulls it?
> > >
> > > Too late. Already pulled and pushed out.
> > >
> > > Looking at the patch, one obvious bug stands out: the new case
> > > statement for SAA7134_BOARD_AVERMEDIA_777 doesn't have a "break" at the
> > > end.
> > >
> > > José, can you test this trivial patch and see if it fixes things?
>
> Yes, this should fix the issue. It passed by my eyes :(
>
> > Mauro, please pull from:
> >
> > http://linuxtv.org/hg/~mkrufky/v4l-dvb
> >
> > for the following:
> >
> > - saa7134: Fix missing 'break' for avermedia card case
>
> Ok, I've updated also master development tree at
> http://linuxtv.org/hg/v4l-dvb
>
> Pasky,
>
> Please test it also.
>
> Cheers,
> Mauro.
The Avermedia 777 is working perfectly again with the current v4l-dvb tree. No
more misbehaviours. Looks like you guys addressed and resolved the issue
quite fast :)
At the moment I can't give the remote control a try because lirc doesn't
compile against version 2.6.18 of the kernel. If that lirc issue gets solved,
I will try to use it as soon as I can.
All the best.
next prev parent reply other threads:[~2006-11-14 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611131711.46626.j.suarez.agapito@gmail.com>
2006-11-13 16:32 ` [linux-dvb] Avermedia 777 misbehaves after remote hack merged into v4l-dvb tree Michael Krufky
2006-11-13 16:44 ` Linus Torvalds
2006-11-13 21:09 ` Michael Krufky
2006-11-13 21:23 ` Mauro Carvalho Chehab
2006-11-14 3:45 ` José Suárez [this message]
2006-11-14 4:28 ` Petr Baudis
2006-11-13 21:17 ` Petr Baudis
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=200611140445.30269.j.suarez.agapito@gmail.com \
--to=j.suarez.agapito@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mkrufky@linuxtv.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.org \
--cc=v4l-dvb-maintainer@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.