From: Sean Young <sean@mess.org>
To: Vincent McIntyre <vincent.mcintyre@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults)
Date: Wed, 8 Feb 2017 13:37:41 +0000 [thread overview]
Message-ID: <20170208133741.GA4405@gofer.mess.org> (raw)
In-Reply-To: <CAEsFdVPeL0APCPCA3BLscTY=yDbqH1Fgi77xu1L-VMQ9TWy99Q@mail.gmail.com>
Hi Vincent,
On Wed, Feb 08, 2017 at 10:30:30PM +1100, Vincent McIntyre wrote:
> Hi
>
> I have been working with Sean on figuring out the protocol used by a
> dvico remote.
> I thought the patch he sent was at fault but I backed it out and tried again.
>
> I've attached a full dmesg but the core of it is when dvb_usb_cxusb
> tries to load:
>
> [ 7.858907] WARNING: You are using an experimental version of the
> media stack.
> As the driver is backported to an older kernel, it doesn't offer
> enough quality for its usage in production.
> Use it with care.
> Latest git patches (needed if you report a bug to
> linux-media@vger.kernel.org):
> 47b037a0512d9f8675ec2693bed46c8ea6a884ab [media]
> v4l2-async: failing functions shouldn't have side effects
> 79a2eda80c6dab79790c308d9f50ecd2e5021ba3 [media]
> mantis_dvb: fix some error codes in mantis_dvb_init()
> c2987aaf0c9c2bcb0d4c5902d61473d9aa018a3d [media]
> exynos-gsc: Avoid spamming the log on VIDIOC_TRY_FMT
> [ 7.861968] dvb_usb_af9035 1-4:1.0: prechip_version=83
> chip_version=02 chip_type=9135
> [ 7.887476] dvb_usb_cxusb: disagrees about version of symbol
> dvb_usb_generic_rw
> [ 7.887477] dvb_usb_cxusb: Unknown symbol dvb_usb_generic_rw (err -22)
-snip-
This is a problem with media_build. I'm not familiar with media_build, I
did try it out last night (for the first time) and got the same issue on
Ubuntu 16.04. I haven't been able to figure out what the problem is yet.
I'll have a look again tonight or tomorrow night. In the mean time, if
anyone else knows then that would be great. :)
Sean
next prev parent reply other threads:[~2017-02-08 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 11:30 [regression] dvb_usb_cxusb (was Re: ir-keytable: infinite loops, segfaults) Vincent McIntyre
2017-02-08 13:37 ` Sean Young [this message]
2017-02-13 20:53 ` Vincent McIntyre
2017-02-15 15:14 ` Sean Young
[not found] ` <CAEsFdVNXCO4n8tMVpKsYme1K1qH1Nm0zAwCFJgS8sfuCiTHbhw@mail.gmail.com>
2017-02-16 13:09 ` Fwd: " Vincent McIntyre
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=20170208133741.GA4405@gofer.mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.kernel.org \
--cc=vincent.mcintyre@gmail.com \
/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