All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Walls <awalls@radix.net>
To: Brandon Jenkins <bcjenkins@tvwhere.com>
Cc: ivtv-devel@ivtvdriver.org, linux-media@vger.kernel.org
Subject: Re: cx18: Reprise of YUV frame alignment improvements
Date: Wed, 11 Nov 2009 20:06:46 -0500	[thread overview]
Message-ID: <1257988006.4065.4.camel@palomino.walls.org> (raw)
In-Reply-To: <de8cad4d0911111638m3de0d417x60d71d8d331e03f0@mail.gmail.com>

On Wed, 2009-11-11 at 19:38 -0500, Brandon Jenkins wrote:
> On Tue, Nov 10, 2009 at 11:31 PM, Andy Walls <awalls@radix.net> wrote:
> >
> > Could folks give this cx18 code a test to make sure their primary use
> > cases didn't break?
> >
> >
> > Regards,
> > Andy
> >
> Andy,
> 
> I have loaded the drivers (also pulling in Devin's change request too)
> and am running with 3 cards and SageTV. I'll let you know if something
> pops up, but nothing thus far.
> 
> Brandon


Thanks a bunch.  It's nice to have someone with a system capable of
being highly loaded to try to break things. :)

For myself, after 1 day I haven't noticed anything.  Though my normal
use case is simple live Digital TV viewing with MythTV - not terribly
stressing.

I assume you mean the mxl5005s and s5h1409 changes for clear QAM when
you say Devin's change.

Regards,
Andy


  reply	other threads:[~2009-11-12  1:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11  4:31 cx18: Reprise of YUV frame alignment improvements Andy Walls
2009-11-12  0:38 ` Brandon Jenkins
2009-11-12  1:06   ` Andy Walls [this message]
2009-11-12  1:23     ` Brandon Jenkins
2009-11-23  3:04 ` Devin Heitmueller
2009-11-23 12:12   ` Andy Walls
2009-11-23 12:32     ` Andy Walls
2009-11-23 17:09     ` Devin Heitmueller
2009-11-24  1:49       ` Andy Walls
2009-11-24 17:57         ` Devin Heitmueller
2009-11-24 23:39           ` Andy Walls
2009-11-25 16:43             ` Devin Heitmueller

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=1257988006.4065.4.camel@palomino.walls.org \
    --to=awalls@radix.net \
    --cc=bcjenkins@tvwhere.com \
    --cc=ivtv-devel@ivtvdriver.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 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.