linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ole Ernst <olebowle@gmx.com>
To: linux-media@vger.kernel.org
Cc: nibble.max@gmail.com, crope@iki.fi, olli.salonen@iki.fi
Subject: cx23885: DVBSky S952 dvb_register failed err = -22
Date: Sat, 14 Mar 2015 20:54:52 +0100	[thread overview]
Message-ID: <5504920C.7080806@gmx.com> (raw)

Hi,

using linux-3.19.1-1 (Archlinux) I get the following output while
booting without the media-build-tree provided by DVBSky:

cx23885 driver version 0.0.4 loaded
cx23885 0000:04:00.0: enabling device (0000 -> 0002)
CORE cx23885[0]: subsystem: 4254:0952, board: DVBSky S952
[card=50,autodetected]
cx25840 3-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0])
cx25840 3-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-2: m88ds3103_attach: chip_id=70
i2c i2c-2: Added multiplexed i2c bus 4
cx23885_dvb_register() dvb_register failed err = -22
cx23885_dev_setup() Failed to register dvb adapters on VID_B
cx23885_dvb_register() allocating 1 frontend(s)
cx23885[0]: cx23885 based dvb card
i2c i2c-1: m88ds3103_attach: chip_id=70
i2c i2c-1: Added multiplexed i2c bus 4
cx23885_dvb_register() dvb_register failed err = -22
cx23885_dev_setup() Failed to register dvb on VID_C
cx23885_dev_checkrevision() Hardware revision = 0xa5
cx23885[0]/0: found at 0000:04:00.0, rev: 4, irq: 17, latency: 0, mmio:
0xf7200000

Obviously there are no device in /dev/dvb. Using the media-build-tree
works just fine though. The following firmware files are installed in
/usr/lib/firmware:
dvb-demod-m88ds3103.fw
dvb-demod-m88rs6000.fw
dvb-demod-si2168-a20-01.fw
dvb-demod-si2168-a30-01.fw
dvb-demod-si2168-b40-01.fw
dvb-fe-ds300x.fw
dvb-fe-ds3103.fw
dvb-fe-rs6000.fw
dvb-tuner-si2158-a20-01.fw

Output of lspci -vvvnn:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/lscpi

I also set the module parameters debug, i2c_debug, irq_debug and
irq_debug in cx23885.
The output is pretty verbose and can be found here:
https://gist.githubusercontent.com/olebowle/6a4108363a9d1f7dd033/raw/debug.log

Thanks,
Ole

             reply	other threads:[~2015-03-14 19:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-14 19:54 Ole Ernst [this message]
2015-03-15 10:26 ` cx23885: DVBSky S952 dvb_register failed err = -22 Ole Ernst
2015-03-15 10:49   ` Antti Palosaari
2015-03-15 11:07     ` Ole Ernst
2015-03-17  1:53     ` Nibble Max
2015-03-17 18:32       ` Ole Ernst
2015-03-18  1:40       ` Nibble Max
2015-03-18  9:06         ` Ole Ernst
2015-03-23 18:08           ` Antti Palosaari
2015-03-23 21:12             ` Ole Ernst
2015-03-23 22:52               ` Antti Palosaari
2015-03-24 12:25                 ` Ole Ernst
2015-03-24 12:54                   ` Antti Palosaari
2015-03-24 14:52                     ` Ole Ernst
2015-03-24 15:22                       ` Antti Palosaari
2015-03-24 19:51                         ` Ole Ernst
2015-03-27 17:24                           ` Ole Ernst
2015-03-27 17:46                             ` Antti Palosaari

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=5504920C.7080806@gmx.com \
    --to=olebowle@gmx.com \
    --cc=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=nibble.max@gmail.com \
    --cc=olli.salonen@iki.fi \
    /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).