Linux Media Controller development
 help / color / mirror / Atom feed
From: Oliver Endriss <o.endriss@gmx.de>
To: Jaroslav Klaus <jaroslav.klaus@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: TS discontinuity with TT S-2300
Date: Sun, 27 Jun 2010 14:37:00 +0200	[thread overview]
Message-ID: <201006271437.01502@orion.escape-edv.de> (raw)
In-Reply-To: <1CF58597-201D-4448-A80C-55815811753E@gmail.com>

Hi,

On Sunday 27 June 2010 01:05:57 Jaroslav Klaus wrote:
> Hi,
> 
> I'm loosing TS packets in my dual CAM premium TT S-2300 card (av7110+saa7146).
> 
> Is it possible the problem is in firmware? Here is the description:
> 
> 04:00.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
>         Subsystem: Technotrend Systemtechnik GmbH Technotrend/Hauppauge DVB card rev2.3
>         Flags: bus master, medium devsel, latency 32, IRQ 20
>         Memory at fddff000 (32-bit, non-prefetchable) [size=512]
>         Kernel driver in use: dvb
> 
> dvb 0000:04:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
> IRQ 20/: IRQF_DISABLED is not guaranteed on shared IRQs
> saa7146: found saa7146 @ mem ffffc90005248000 (revision 1, irq 20) (0x13c2,0x000e).
> dvb 0000:04:00.0: firmware: requesting dvb-ttpci-01.fw
> DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-S rev2.3)
> adapter has MAC addr = 00:d0:5c:04:2e:ea
> dvb 0000:04:00.0: firmware: requesting av7110/bootcode.bin
> dvb-ttpci: info @ card 0: firm f0240009, rtsl b0250018, vid 71010068, app 80f12623
> dvb-ttpci: firmware @ card 0 supports CI link layer interface
> 
> I've tried also:
>  dvb-ttpci: info @ card 1: firm f0240009, rtsl b0250018, vid 71010068, app 8000261a
>  dvb-ttpci: info @ card 1: firm f0240009, rtsl b0250018, vid 71010068, app 80002622
> without any impact.
> 
> SR of my signal is 27500, 2x official CAMs (videoguard).
> 
> I use dvblast to select 4 TV channels (~ 16 PIDs) from multiplex,
> descramble them and stream them to network. Dvblast reports TS
> discontinuity across all video PIDs only (no audio) usually every
> 1-3 minutes ~80 packets. But sometimes it goes well for tens of
> minutes (up to 1-2hours). Everything seems to be ok with 3 TV channels.
> 
> Do you thing it is av7110 issue? Do you know any relevant limits of
> av7110? What should I test/try more? Thanks 

The full-featured cards are not able to deliver the full bandwidth of a
transponder. It is a limitaion of the board design, not a firmware or
driver issue.

You can fix this by applying the 'full-ts' hardware modification.
For more information follow the link in my signature.

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------

  reply	other threads:[~2010-06-27 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-26 23:05 TS discontinuity with TT S-2300 Jaroslav Klaus
2010-06-27 12:37 ` Oliver Endriss [this message]
2010-06-27 15:23   ` Jaroslav Klaus
2010-06-27 15:56   ` Marko Ristola
2010-06-27 18:25     ` Oliver Endriss
2010-06-27 20:51       ` Marko Ristola

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=201006271437.01502@orion.escape-edv.de \
    --to=o.endriss@gmx.de \
    --cc=jaroslav.klaus@gmail.com \
    --cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox