From: Steven Toth <stoth@linuxtv.org>
To: stev391@email.com
Cc: linux dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] cx23885 driver and DMA timeouts
Date: Mon, 23 Jun 2008 08:51:10 -0400 [thread overview]
Message-ID: <485F9C3E.50309@linuxtv.org> (raw)
In-Reply-To: <20080622121058.122F7BE4078@ws1-9.us4.outblaze.com>
stev391@email.com wrote:
> Steven,
>
> The card works perfectly using Chris Pascoe's branch, I can use both
> tuners at the same time. It only stuffs up when I try and merge the
> relevant sections into tip, as per the patch I attached in the previous
> email. So this eliminates bios/hardware faults. I can also try in
> windows for you, but I'm sure this is not the fault.
>
> I would like to run a more modern version of the hg code as I have other
> cards sitting around that could go in the same system and also I fear
> that if somebody doesn't do the work to get it into tip, support will
> disappear for newer kernels.
>
> Thanks for help, any further advice?
> (Also you lost me a bit with sram and risc, is this for the
> microprocessor on the tv card or is it on my motherboard/cpu? And do you
> have any documentation about them so I can learn more about it?)
>
> Stephen.
>
> ----- Original Message -----
> From: "Steven Toth"
> To: stev391@email.com
> Subject: Re: [linux-dvb] cx23885 driver and DMA timeouts
> Date: Sat, 21 Jun 2008 08:54:39 -0400
>
>
>
> > As soon as I try to access both cards at the same time it breaks
> > and only a full computer restart will fix it, i have tried
> > unloading all the modules that I can find that this card uses and
> > loading them again. I get the syslog attached below (cx23885 with
> > debug =1). It doesn't matter what progam i use to access them
> > (tried gxine, totem, mythtv) it all works the same, only one at a
> > time or it breaks.
>
> If the vidb and vidc (ts1 / ts2) bridge streams each single channel
> correctly, but not both together then this is either a sram
> configuration issue (the risc engine's workspace is being corrupted
> by another risc channel), or your system has a pcie compatibility
> issue.
>
> I've seen both of these issues in the past.
>
> I don't have a hardware product with demodulators on vidb and c, so
> that's not something I can repro.
>
> Can you dual boot the same system under windows and remove any pcie
> compatibility doubts?
>
> - Steve
No need to try windows, if you have the driver already running (pascoe's
patches) then your chipset and hardware are fine.
Sounds like you have a simple merge issue.
Try to figure out which parts of the merge actually create the problem
then bring that issue back to this list for discussion.
Regards,
- Steve
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-06-23 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 12:10 [linux-dvb] cx23885 driver and DMA timeouts stev391
2008-06-23 12:51 ` Steven Toth [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-25 22:32 stev391
2008-06-25 22:53 ` Steven Toth
2008-06-21 5:22 stev391
2008-06-21 12:54 ` Steven Toth
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=485F9C3E.50309@linuxtv.org \
--to=stoth@linuxtv.org \
--cc=linux-dvb@linuxtv.org \
--cc=stev391@email.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