public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Lars Hanisch <dvb@cinnamon-sage.de>
To: linux-media@vger.kernel.org
Subject: Re: cx18: where do the transport stream PIDs come from?
Date: Tue, 02 Mar 2010 23:18:30 +0100	[thread overview]
Message-ID: <4B8D8EB6.4030305@cinnamon-sage.de> (raw)
In-Reply-To: <1267362273.3106.12.camel@palomino.walls.org>

Am 28.02.2010 14:04, schrieb Andy Walls:
> On Fri, 2010-02-26 at 17:23 +0100, Lars Hanisch wrote:
>> Hi,
>>
>>    while working on a small test app which repacks the ivtv-PS into a TS, I received a sample from a cx18-based card. The
>> TS contains the video PID 301, audio PID 300 and PCR pid 101.
>>
>>    Where do these PIDs come from, are they set by the driver or are they firmware given?
>
> For analog captures, for which the firmware creates the TS, the firmware
> sets them.

  That's what I thought. So I will use the same IDs for my conversion of an ivtv-PS.

>
>
>>    Is it possible to change them?
>
> It is not possible to tell the firmware to change them.  There are two
> documented CX23418 API commands in cx23418.h:
>
> CX18_CPU_SET_VIDEO_PID
> CX18_CPU_SET_AUDIO_PID
>
> Unfortunately, I know they do nothing and will always directly return
> 0x200800ff, which is a CX23418 API error code.

  Good to know.

Thanks!
Lars.

>
> Regards,
> Andy
>
>> Regards,
>> Lars.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2010-03-02 22:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26 16:23 cx18: where do the transport stream PIDs come from? Lars Hanisch
2010-02-28 13:04 ` Andy Walls
2010-03-02 22:18   ` Lars Hanisch [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=4B8D8EB6.4030305@cinnamon-sage.de \
    --to=dvb@cinnamon-sage.de \
    --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