From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: <linux-media@vger.kernel.org>
Subject: Re: XC5000 improvements: call for testers!
Date: Wed, 13 May 2009 12:04:20 -0700 [thread overview]
Message-ID: <005f01c9d3fd$e2ee8980$0a00a8c0@vorg> (raw)
In-Reply-To: 829197380905121356y1d76d73eu4738e3e926c11d27@mail.gmail.com
----- Original Message -----
From: "Devin Heitmueller" <dheitmueller@kernellabs.com>
To: "Britney Fransen" <britney.fransen@gmail.com>
Cc: "Devin Heitmueller" <devin.heitmueller@gmail.com>; "Linux Media Mailing List" <linux-media@vger.kernel.org>
Sent: Tuesday, May 12, 2009 1:56 PM
Subject: Re: XC5000 improvements: call for testers!
> On Tue, May 12, 2009 at 4:50 PM, Britney Fransen
> <britney.fransen@gmail.com> wrote:
> > I finally had some time to do some more testing with the beta2 tree and I
> > think most of the issues I had were user error. Not exactly sure what I did
> > wrong before but I am not seeing the reception issues or any regressions on
> > the digital side anymore. I think why I thought I was seeing QAM64 was
> > because I was using the wrong tuner. With the beta2 tree my 950q is now
> > adapter1, before it was always adapter2. That could be part of what I
> > thought was the reception regression as well.
> >
> > Thanks,
> > Britney
>
> Hello Britney,
>
> Thank you for taking the time to isolate/debug the situation. The
> changes should have no effect on the order of adapter1/adapter2.
> Could have just been a coincidence or the order in which you plugged
> in the devices compared to what they usually are at boot time.
>
> Glad to see that there are no longer any issues. Once I get one
> outstanding Pinnacle 800i fix in, I will issue a PULL request and this
> will go into the mainline.
>
> Cheers,
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
So when this goes main, next time we update from v4l we need the new firmware right?
next prev parent reply other threads:[~2009-05-13 19:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 4:14 XC5000 improvements: call for testers! Devin Heitmueller
[not found] ` <cb69f9670905052347k4117de32lc78290e7356dd14e@mail.gmail.com>
2009-05-06 13:02 ` Devin Heitmueller
[not found] ` <cb69f9670905060803ucce5b66v587f385069adad3f@mail.gmail.com>
2009-05-06 15:16 ` Devin Heitmueller
2009-05-06 21:46 ` Frank Dischner
2009-05-06 21:49 ` Devin Heitmueller
[not found] ` <cb69f9670905122313s340492d4qcbe8e91862a50b2c@mail.gmail.com>
2009-05-13 15:01 ` Devin Heitmueller
2009-05-06 18:42 ` Britney Fransen
2009-05-06 18:43 ` Britney Fransen
2009-05-06 18:50 ` Devin Heitmueller
2009-05-06 21:02 ` Britney Fransen
2009-05-06 21:10 ` Devin Heitmueller
2009-05-06 21:45 ` Britney Fransen
2009-05-06 21:52 ` Devin Heitmueller
2009-05-07 3:55 ` Devin Heitmueller
2009-05-12 20:50 ` Britney Fransen
2009-05-12 20:56 ` Devin Heitmueller
2009-05-12 20:59 ` Britney Fransen
2009-05-12 21:12 ` Devin Heitmueller
2009-05-13 19:04 ` Timothy D. Lenz [this message]
2009-05-13 19:24 ` Devin Heitmueller
2009-05-13 22:26 ` Vanessa Ezekowitz
2009-05-13 22:37 ` Devin Heitmueller
2009-05-06 21:19 ` Devin Heitmueller
2009-05-07 0:09 ` John R.
-- strict thread matches above, loose matches on Subject: below --
2009-05-07 11:21 John R.
2009-05-08 13:54 ` 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='005f01c9d3fd$e2ee8980$0a00a8c0@vorg' \
--to=tlenz@vorgon.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