Andreas Oberritter wrote:
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.
Ngene CI appears as both ca0 and cam0 (or sec0). The ca0 node is used
as usual, to setup the CAM. The cam0 (or sec0) node is used to read/write
transport stream. To me it looks like an extension of the current API.
The sec name needs changing obviously, but there seem to be some other
problems too.
If it was that easy to fix, it wouldn't be in staging today.
Regards,
Andreas
Regards,
Martin
--
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
