On 03/04/2016 07:11 AM, Krzysztof Hałasa wrote: > Hans Verkuil <hverkuil@xxxxxxxxx> writes: > >>> Staging is meant for completely different situation - for immature, >>> incomplete code. It has nothing to do with the case. >> >> It can be for anything that prevents it from being mainlined. It was (still is?) >> used for mature android drivers, for example. > > What is preventing my driver from being mainlined? I have two drivers with different feature sets. Only one can be active at a time. I have to make a choice which one I'll take and Ezequiel's version has functionality (audio, interlaced support) which matches best with existing v4l applications and the typical use cases. I'm not going to have two drivers for the same hw in the media subsystem since only one can be active anyway. My decision, although Mauro can of course decide otherwise. I am OK with adding your driver to staging in the hope that someone will merged the functionalities of the two to make a new and better driver. Whether that means that Ezequiel's code is merged into yours or vice versa, I really don't care. My goal is to provide the end-user with the best experience, and this is IMHO the best option given the hand I've been dealt. I ordered a tw6869-based PCIe card so I can do testing myself once it has arrived. Regards, Hans -- 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
