public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
* cx18: where do the transport stream PIDs come from?
@ 2010-02-26 16:23 Lars Hanisch
  2010-02-28 13:04 ` Andy Walls
  0 siblings, 1 reply; 3+ messages in thread
From: Lars Hanisch @ 2010-02-26 16:23 UTC (permalink / raw)
  To: linux-media

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?
  Is it possible to change them?

Regards,
Lars.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: cx18: where do the transport stream PIDs come from?
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Andy Walls @ 2010-02-28 13:04 UTC (permalink / raw)
  To: Lars Hanisch; +Cc: linux-media

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.


>   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.

Regards,
Andy

> Regards,
> Lars.



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: cx18: where do the transport stream PIDs come from?
  2010-02-28 13:04 ` Andy Walls
@ 2010-03-02 22:18   ` Lars Hanisch
  0 siblings, 0 replies; 3+ messages in thread
From: Lars Hanisch @ 2010-03-02 22:18 UTC (permalink / raw)
  To: linux-media

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
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2010-03-02 22:18 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox