Hi, I'm currently porting the GPL linux-avc2210k driver ( http://www.freelists.org/archive/linux-avc2210k/ ) to V4L2. The current version has it's own API that makes it incompatible with any software except for specific user space apps (avcctrl, avctune) bundled with the driver. Since development seems to have halted for some time now, I had no other choice than get my hands dirty :( For the most part this task seems quite straight forward it's mostly a matter of changing ioctls to V4L2 and add some missing support, there are however a few points that I need some advice on: For the box to function it needs a firmware upload. Currently this is managed by a udev script that in turn calls an application (multiload) that provides for the upload. What I would like to know is, if this the best way to handle it? The problem with this process is that it will always require installing and configuring additional software (multiload and udev script), besides the firmware. Is there any simpler/standard way of handling these firmware uploads ? Regards, Paulo -- 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
