public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Roland Scheidegger <rscheidegger_lists@hispeed.ch>
To: Ruediger Dohmhardt <ruediger.dohmhardt@freenet.de>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] mantis crash...
Date: Mon, 05 May 2008 16:02:13 +0200	[thread overview]
Message-ID: <481F1365.50808@hispeed.ch> (raw)
In-Reply-To: <481CD27A.9080300@freenet.de>

Ruediger Dohmhardt wrote:
> Roland Scheidegger schrieb:
>> This was reported before, the current mantis driver will cause a
>> page fault in mantis_dvb_start_feed.
>> 
> Dear Roland,
> 
> I applied your patch to the code I got from
> 
> http://jusst.de/hg/mantis
> 
> Now the mantis driver (for 2033) works fine for me.
> 
> Setup: 2.6.22.19 vdr-1.5.18/xineliboutput
> 
> Unfortunately, as soon as I insert the CAM module, the driver
> crashes. According to the logfile, it looks that "vdr" still gets the
> information about the CAM and tries to access it. Then the driver
> crashes.  Maybe  someone  still has an idea how to dig into this.
Yes, the crash is due to the same (or similar) bogus hif reads/writes as
that fixed in the patch obviously - that code gets only used with a CAM.
There are mmreads/mmwrites to MANTIS_GPIF_HIFADDR, MANTIS_GPIF_HIFDIN
and MANTIS_GPIF_HIFDOUT - I'm sure all of them will blow up (they are
all the exact same value anyway).
But I wouldn't know how to fix this - I suspect those values are
actually masks which you'd or with some other values for accessing
values not directly accessible in registers. That's just speculation
however, I don't even have a clue what "HIF" stands for (well I guess
something with interface?). Fixing it would require a chip datasheet at
least (or (working) example code), or reverse engeneering or whatever.
Even if this particular hif read/write issue was fixed I'd highly doubt
though the cam code would actually work in its current state -
apparently it was never tested nor working. So Manu Abraham needs to fix
it I suspect - unfortunately there were no updates for over two weeks now.

Roland


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

      reply	other threads:[~2008-05-05 14:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 20:44 [linux-dvb] mantis crash Roland Scheidegger
2008-05-03 21:00 ` Ruediger Dohmhardt
2008-05-05 14:02   ` Roland Scheidegger [this message]

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=481F1365.50808@hispeed.ch \
    --to=rscheidegger_lists@hispeed.ch \
    --cc=linux-dvb@linuxtv.org \
    --cc=ruediger.dohmhardt@freenet.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