On Sat, Jun 19, 2010 at 8:09 PM, Michael Krufky <mkrufky@xxxxxxxxxxxxxx> wrote: > Mauro, > > This adds the ability for drivers to send the received raw payload to > the dvr device, in cases of newer delivery systems that do not deliver > transport stream and do not require usage of the kernel demux. In > these cases, the data can be fully decoded by a userspace application > / library. > > For a driver to deliver the raw payload, simply use the function > "dvb_dmx_swfilter_raw" instead of "dvb_dmx_swfilter" or RAW without an additional identifier doesn't make much sense, how should an application figure out what a RAW stream is? Is it network data? is /dev/urandom data? how should that be handle by an application. There should be another 'hint' somewhere about the fileformat. This somewhat influences the internal/external DVB API, without proper identification it shouldn't be added as it is. Markus > "dvb_dmx_swfilter_204", as shown in the dvb-usb patch. > > Please pull from: > > http://kernellabs.com/hg/~mkrufky/raw-payload > > for the following: > > - dvb-demux: add functionality to send raw payload to the dvr device > - dvb-usb: add support for dvb-usb-adapters that deliver raw payload > > dvb-core/dvb_demux.c | 11 +++++++++++ > dvb-core/dvb_demux.h | 2 ++ > dvb-usb/dvb-usb-urb.c | 10 ++++++++++ > dvb-usb/dvb-usb.h | 1 + > 4 files changed, 24 insertions(+) > > Cheers, > > Mike Krufky > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
