Hello Andreas So if I understand correctly due to HW limitations back then, if in user-space we want to get data of two PSI tables that share the same PID, we could only setup one section filter with that PID and the user-space needs to do the extra filtering (to parse and separate the sections belonging to each table)? Regards, Hamad -----Original Message----- From: linux-media-owner@xxxxxxxxxxxxxxx [mailto:linux-media-owner@xxxxxxxxxxxxxxx] On Behalf Of Andreas Oberritter Sent: Thursday, December 01, 2011 3:37 PM To: Hamad Kadmany Cc: linux-media@xxxxxxxxxxxxxxx Subject: Re: Support for multiple section feeds with same PIDs Hello Hamad, On 29.11.2011 09:05, Hamad Kadmany wrote: > Question on the current behavior of dvb_dmxdev_filter_start (dmxdev.c) > > In case of DMXDEV_TYPE_SEC, the code restricts of having multiple sections > feeds allocated (allocate_section_feed) with same PID. From my experience, > applications might request allocating several section feeds using same PID > but with different filters (for example, in DVB standard, SDT and BAT tables > have same PID). > > The current implementation only supports of having multiple filters on the > same section feed. > > Any special reason why it was implemented this way? AFAIR, if you created more than one PID filter on the same PID, only one filter would see data on most or all hardware back then. So if you have multiple filters on the same PID, then the real filter you're setting should be a merged version of those filters. If you use dvb_demux, it will do the necessary post-processing for you. This driver implements section filtering: http://cvs.tuxbox.org/cgi-bin/viewcvs.cgi/tuxbox/driver/dvb/drivers/media/dv b/avia/avia_gt_napi.c?rev=1.208&view=markup Regards, Andreas -- 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