From: shuah <shuah@kernel.org>
To: Nathan Royce <nroycea+kernel@gmail.com>
Cc: Brad Love <brad@nextdimension.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: Tue, 20 Aug 2019 07:56:55 -0600 [thread overview]
Message-ID: <94bfd12e-e9d4-1e6a-a18f-742e251f5cd9@kernel.org> (raw)
In-Reply-To: <CALaQ_hrPZ7LMBvuHnCLayxHoVFi5U0gtxF-33-ehR=phRs3D5A@mail.gmail.com>
On 8/20/19 12:58 AM, Nathan Royce wrote:
> While your mention of quirks-table.h certainly had possibilities, I'm
> afraid adding the "AU0828_DEVICE(0x05e1, 0x0400, "Hauppauge",
> "Woodbury")," entry for my tuner did not make any difference regarding
> the "Tuner is busy. Error -19" message.
>
> I don't know if this means anything, but I see
> https://patchwork.kernel.org/patch/97726/ from 2010 which contains
> changes for the 0x0400 model. I guess it never got pulled in.
>
> Really, it's fine for me just to hang back at v5.1 for a year or two
> until ATSC 3.0 USB tuners come out at a reasonable price.
>
Hi Nathan,
The tuner busy error code is ENODEV. It appears some devices aren't
created on your system. Would it be possible for you to send me your
config and a complete dmesg.
I am curious if /dev/media0 or /dev/media1 present on your system.
Not having this could explain the ENODEV you are seeing.
thanks,
-- Shuah
next prev parent reply other threads:[~2019-08-20 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 18:18 Kernel 5.2.8 - au0828 - Tuner Is Busy 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
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 [this message]
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=94bfd12e-e9d4-1e6a-a18f-742e251f5cd9@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;
as well as URLs for NNTP newsgroup(s).