From: shuah <shuah@kernel.org>
To: Nathan Royce <nroycea+kernel@gmail.com>,
Brad Love <brad@nextdimension.cc>
Cc: sean@mess.org, Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
shuah <shuah@kernel.org>
Subject: Re: Kernel 5.2.8 - au0828 - Tuner Is Busy
Date: Mon, 19 Aug 2019 14:49:28 -0600 [thread overview]
Message-ID: <eada38a3-258b-52ff-94a7-b8877899267e@kernel.org> (raw)
In-Reply-To: <CALaQ_hqEZ-kco1esyB4mk0z9Q9Xt1XZsgYKR7gSdF7COERKoOA@mail.gmail.com>
On 8/16/19 7:15 PM, Nathan Royce wrote:
> On Fri, Aug 16, 2019 at 1:42 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
>> If you revert that one commit, does things start working again?
>>
>> thanks,
>>
>> greg k-h
> Hey Greg, I just got finished building it after running "$ git revert
> 812658d88d26" and verifying it reverted by comparing one of the files
> from git log -p, but alas, no joy.
>
> On Fri, Aug 16, 2019 at 5:41 PM Brad Love <brad@nextdimension.cc> wrote:
>>
>> Hi Nathan,
>>
>> I don't have a "woodbury", but I have a Hauppauge 950Q sitting around
>> and tested it on latest mainline kernel. w_scan is ok and streaming is
>> fine. There's no unexpected errors. The 950Q uses the same au0828 bridge
>> and au8522 demod as woodbury, but a different tuner. Your problem
>> wouldn't appear to be a general au0828 issue.
>>
Thanks Brad!
>> You might have to check out git bisect. That will be the quickest way to
>> get to the bottom, if you've got points A and B, and are
>> building/running your own kernel.
>>
>> Cheers,
>>
>> Brad
> Thanks Brad, I'll explore bisecting and hopefully will be able to
> narrow down the cause.
> I wasn't running my own kernel, but rather using the Arch Linux kernel
> and modding the one module and putting it in "extramodules".
>
Hi Nathan,
Just catching up with this thread. Let me know what you find. Can you
build your own kernel and see what you can find?
thanks,
-- Shuah
next prev parent reply other threads:[~2019-08-19 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 18:18 Nathan Royce
2019-08-16 18:42 ` Greg Kroah-Hartman
2019-08-16 22:41 ` Brad Love
2019-08-17 1:15 ` Nathan Royce
2019-08-19 20:49 ` shuah [this message]
2019-08-19 21:44 ` shuah
2019-08-19 23:02 ` Nathan Royce
2019-08-20 6:58 ` Nathan Royce
2019-08-20 13:56 ` shuah
2019-08-26 22:32 ` shuah
2019-08-19 23:03 ` Nathan Royce
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=eada38a3-258b-52ff-94a7-b8877899267e@kernel.org \
--to=shuah@kernel.org \
--cc=brad@nextdimension.cc \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=nroycea+kernel@gmail.com \
--cc=sean@mess.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome