All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Sager <john@sager.me.uk>
To: Andy Walls <awalls@radix.net>
Cc: LinuxTV-DVB <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] pci_abort messages from cx88 driver
Date: Thu, 18 Dec 2008 14:38:54 +0000	[thread overview]
Message-ID: <494A607E.9030105@sager.me.uk> (raw)
In-Reply-To: <1229552900.3109.24.camel@palomino.walls.org>

Andy,

Thanks for the reply.

Andy Walls wrote:

> 
> You've logically leaped too far.  You can only say that the aborted PCI
> transfers, if any actually happened, didn't matter to apparent proper
> operation of the device in it's current mode of operation.
> 
> That said, maybe the best course of action is to ignore PCI aborts when
> a capture is ongoing.  It however, may not be the best idea to ignore
> such errors when setting up for a capture or controlling I2C device
> through the chip.

The interrupts in question are specifically related to the transport
stream.

> 
>>
>> It may be worth fixing this in the main code to hide the problem for
>> unfortunate users of this & related cards until the real problem is
>> found. Unfortunately I doubt I can help there as a detailed knowledge
>> of the Conexant PCI interface device is probably required to pursue it.
> 
> Maybe not.  Look at the cx18 driver where a similar issue was
> confronted.

Yuk. I see what you mean. I don't think I really want to go that far.
The fix is minor so I don't mind patching kernels for my own use
when they get upgraded. If I start getting other problems as a consequence
I may just give up on the card but fingers-crossed it's working OK
for now.

regards,

John

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

      reply	other threads:[~2008-12-18 14:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17 14:59 [linux-dvb] pci_abort messages from cx88 driver John Sager
2008-12-17 22:28 ` Andy Walls
2008-12-18 14:38   ` John Sager [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=494A607E.9030105@sager.me.uk \
    --to=john@sager.me.uk \
    --cc=awalls@radix.net \
    --cc=linux-dvb@linuxtv.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.