>> On 03/10/2011 04:29 PM, Issa Gorissen wrote: >>> As the cxd20099 driver is in staging due to abuse of the sec0 device, > this >>> patch renames it to cam0. The sec0 device is not in use and can be > removed >> >> That doesn't solve anything. Besides, your patch doesn't even do what >> you describe. >> >> Wouldn't it be possible to extend the current CA API? If not, shouldn't >> a new API be created that covers both old and new requirements? >> >> It's rather unintuitive that some CAMs appear as ca0, while others as cam0. >> >> If it was that easy to fix, it wouldn't be in staging today. >> >> Regards, >> Andreas > > > Yes indeed, this patch is missing the update of dnames arrays in dvbdev.c > > Now, according to Mauro comments, he has put this code into staging because of > the usage of sec0 name for a cam device. > > Please comment on Oliver's explanations from this thread > > http://www.mail-archive.com/linux-media@xxxxxxxxxxxxxxx/msg26901.html Oliver explained that he's not going to put work into this driver, because he's not using it. Until now, I haven't heard any reasons for just adding another device node other than it being easier than defining a proper interface. The fact that a solution "just works as is" is not sufficient to move a driver from staging. IMO the CI driver should not have been included at all in its current shape. 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
