Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Re: V4 API proposal
- To: "Johannes Stezenbach" <js@convergence.de>
- Subject: [linux-dvb] Re: V4 API proposal
- From: "Haber, Thomas" <THaber@tee.toshiba.de>
- Date: Mon, 10 Mar 2003 14:33:48 +0100
- Cc: <linux-dvb@linuxtv.org>
- Content-class: urn:content-classes:message
- Content-transfer-encoding: quoted-printable
- Content-type: text/plain;charset="iso-8859-1"
- Sender: linux-dvb-bounce@linuxtv.org
- Thread-index: AcLnCIqkTZUsJLf9Qx2nboxGn5FHmwAAJKnA
- Thread-topic: [linux-dvb] Re: V4 API proposal
Hi Johannes
>
> Question: Is there hardware support for dmx_header_filter_t? If not we
> should not add DMX_SET_EXT_FILTER to the API, let the
> application/middleware
> do it. We could add DMX_PAYLOAD_ONLY (and DMX_HEADER_ONLY?)
> to the flags
> for DMX_SET_FILTER, though (if it makes sense).
I guess, you misunderstood this.
It should have been a replacement for DMX_SET_SEC_FILTER.
>
> One other thing:
> Currently the API makes no guarantee on data alignment when you read()
> PES data from the demux. For sections, it is guaranteed that
> each read()
> wil get exactly one section with the start of the section at the start
> of the buffer, provided the buffer is large enough. If the
> buffer is too
> small, consecutive read()s will get the remainder of the section.
>
> We could try to do the same for PES filters, or shouldn't we?
>
Could make sense. At least there should be a flag requesting this.
> (Currently middleware code that deals with PES filter output
> must search
> for the PES packet start code manually; that sucks.)
>
> Johannes
>
Regards,
thomas
--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.
Home |
Main Index |
Thread Index