Hi, Am Mittwoch, den 07.04.2010, 00:39 +0200 schrieb Hans Verkuil: > On Tuesday 06 April 2010 17:16:17 Mike Isely wrote: > > On Tue, 6 Apr 2010, Laurent Pinchart wrote: > > > > > Hi Andy, > > > > > > On Tuesday 06 April 2010 13:06:18 Andy Walls wrote: > > > > On Tue, 2010-04-06 at 08:37 +0200, Hans Verkuil wrote: > > > > > > [snip] [snip] > > code. I don't know if that same strategy could be done in the V4L core. > > If it could, then this would probably alleviate a lot of concerns about > > testing / maintenance going forward. > > In other words, yes, it could do this. And with relatively little work and > completely transparent to all drivers. > > But I have a big question mark whether we really want to go that way. The > good thing about it is that the ioctls remain the primary API, as they should > be. Anything like this will definitely be a phase 3 (or 4, or...), but it > is at least nice to realize how easy it would be. That's a good sign of the > quality of the code. > > Regards, > > Hans that all looks really good now and quite promising, also IR/remote. Maybe too good? About what might be upcoming problems nobody is talking about currently. Never seen before ... I would wonder a lot, if we really should have made it close to such with a lot of buffering all around ;) Well, I guess the time on that beach might be short. Manu gave some pointers previously that HD+ is a serious issue for us, also it seems, that some lower level of firmware starts to hide GPIO's and i2c addresses on recent boards. We likely should stay hackish and able for quick responses and not over-engineer convenience we do not really have. Just my two cents. Cheers, Hermann -- 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
