From: Andy Walls <awalls@md.metrocast.net>
To: me@boris64.net
Cc: linux-media@vger.kernel.org
Subject: Re: TeVii S470 dvb-s2 issues - 2nd try ,)
Date: Fri, 17 Dec 2010 08:12:56 -0500 [thread overview]
Message-ID: <1292591576.2077.19.camel@morgan.silverblock.net> (raw)
In-Reply-To: <201012171219.29473.me@boris64.net>
On Fri, 2010-12-17 at 12:19 +0100, Boris Cuber wrote:
> Hello linux-media people!
>
> I have to problems with my dvb card ("TeVii S470"). I already
> filed 2 bug reports some time ago, but no one seems to have
> noticed/read them, so i'm trying it here now.
> If you need a "full" dmesg, then please take a look at
> https://bugzilla.kernel.org/attachment.cgi?id=40552
>
> 1) "TeVii S470 dvbs-2 card (cx23885) is not usable after
> pm-suspend/resume" https://bugzilla.kernel.org/show_bug.cgi?id=16467
The cx23885 driver does not implement power management. It would likely
take many, many hours of coding and testing to implement it properly.
If you need resume/suspend, use the power management scripts on your
machine to kill all the applications using the TeVii S470, and then
unload the cx23885 module just before suspend.
On resume, have the power management scripts reload the cx23885 module.
> 2) "cx23885: ds3000_writereg: writereg error on =kernel-2.6.36-rc with
> TeVii" S470 dvb-s2 card
> -> https://bugzilla.kernel.org/show_bug.cgi?id=18832
>
> These error messages show up in dmesg while switching channels in
> mplayer/kaffeine.
> [dmesg output]
> [ 919.789976] ds3000_writereg: writereg error(err == -6, reg == 0x03,
> value == 0x11)
They look like I2C bus errors; error -6 is ENXIO, which is probably
coming from cx23885-i2c.c.
The device handled by the ds3000 driver is not responding properly to
the CX23885. It could be that some other device on that I2C bus is hung
up or the ds3000 device itself. Maybe some GPIO settings are set wrong?
The cx23885 module supports an i2c_probe and i2c_debug module option
that will turn on some messages related to i2c.
I really have no other advice, except that if you do a git bisect
process, you may find the commit(s) that caused the problem.
Regards,
Andy
> Are these issues known? If so, are there any fixes yet? When will these
> get into mainline? Could somebody point me into the right direction.
> Can i help somehow to debug these problems?
>
> Thank you in advance.
>
> Regards,
> Boris Cuber
>
> PS: Thank Emanuel for helping me out with this mail ,)
next prev parent reply other threads:[~2010-12-17 13:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 13:29 TeVii S470 dvb-s2 issues Boris Cuber
2010-12-17 3:31 ` Anca Emanuel
2010-12-17 11:19 ` TeVii S470 dvb-s2 issues - 2nd try ,) Boris Cuber
2010-12-17 13:12 ` Andy Walls [this message]
2010-12-18 13:40 ` Boris Cuber
2010-12-18 14:23 ` Andy Walls
2010-12-19 12:31 ` Boris Cuber
2011-01-02 19:01 ` Igor M. Liplianin
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=1292591576.2077.19.camel@morgan.silverblock.net \
--to=awalls@md.metrocast.net \
--cc=linux-media@vger.kernel.org \
--cc=me@boris64.net \
/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