Hans de Goede wrote: >> I would call it media-utils. A nice name and it reflects that it contains >> both dvb and v4l utilities. >> > > Well, the judge is still out on also adding the dvb utils to this git repo. > I'm neutral on that issue, but I will need a co-maintainer for those bits > if they end up in the new v4l-utils repo too. I also don't have any strong feeling about merging dvb utils. The advantage is to share the same release control, but the code is completely separated. There will likely be some developers working on both projects. A deeper look on what we have on userspace, there are 3 categories of software: - apps that handle /dev/v4l/* devices (e. g. V4L2 API hanling); - apps that handle /dev/dvb/* devices (e. g. DVB API handling); - apps that handle /dev/input/* devices (e. g. IR API handling). The last one is, in fact just one code, plus lots of IR tables from all V4L and DVB drivers. The table is created today by the Makefile: it reads the table from the kernel source tree and generates the tables for the userspace util [*]. If we are maintaining separate trees for each class of device, it might make sense to have separate a tree for the IR stuff, but this seems overkill to me, since we'll need to handle 3 separate version controls for each tool class, and, in practice, v4l/dvb users will need to get more than one tree to get full control of his device. So, I prefer to have one tree with all 3 types of utilities. [*] Btw, how Brandon addressed it with the conversion tool? I think we'll need to add some tools there to handle the kernel driver <-> v4l2-apps interdependency, e. g. creating the *.c.xml files needed by the media-specs and importing the IR keymaps from the driver sources. -- Cheers, Mauro -- 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
