On 05/04/2011 03:35 PM, Martin Vidovic wrote: >> >>> Or is there a standard way this is supposed to be handled? >> >> Yes. Since ages. The ioctl is called DMX_SET_SOURCE. > > DMX_SET_SOURCE seems to not be implemented anywhere, all it does is > return EINVAL. I also fail to find any useful documentation about what > it is supposed to do. It is supposed to connect the TS output of frontend X to the TS input of demux Y. Whether you need to manually connect anything depends on your application and hardware environment. It's not required at all when using the software demux, which is what almost all in-tree drivers do. >>> There are no mechanism to connect a frontend with specific dvr or >>> demux devices in the current API. But you demand it for the caio device. >> > > I think there is currently no useful API to connect devices. Every few > months there comes a new device which deprecates how I enumerate devices > and determine types of FE's. Can you describe the most common problems? What do you mean by connecting? > The most useful way to query devices seems to be using HAL, and I think > this is the correct way in Linux, but DVB-API may be lacking with > providing the necessary information. Maybe this is the direction we > should consider? Device names under /dev seem to be irrelevant nowadays. I think in the long run we should look closely at how V4L2 is solving similar problems. 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
