Hi! > > > 2) support for running libv4l2 on mc-based devices. I'd like to do > > > that. > > > > > > Description file would look like. (# comments would not be not part of file). > > > > > > V4L2MEDIADESC > > > 3 # number of files to open > > > /dev/video2 > > > /dev/video6 > > > /dev/video3 > > "Easy" file formats usually means maintenance troubles as new > things are needed, and makes worse for users to write it. > You should take a look at lib/libdvbv5/dvb-file.c, mainly at > fill_entry() and dvb_read_file(). Well, file formats just need to be maintained. > > Instead these should be entity names from the media controller. > > Agreed that it should use MC. Yet, IMHO, the best would be to use > the entity function instead, as entity names might eventually > change on newer versions of the Kernel. Kernel interfaces are not supposed to be changing. > (again, user may specify just name, just function or both) > > > > 3 # number of controls to map. Controls not mentioned here go to > > > # device 0 automatically. Sorted by control id. > > > # Device 0 > > > 00980913 1 > > > 009a0003 1 > > > 009a000a 2 > > I would, instead, encode it as: > > [control white balance] > control_id = 0x00980913 > entity = foo_entity_name Ok, that's really overly complex. If futrue extensibility is concern we can do 0x00980913=whatever. > Allowing both hexadecimal values and control macro names (can easily parsed > from the header file, as we already do for other things with "make > sync"). "Easily" as in "more complex then rest of proposed code combined" :-(. > It should probably be easy to add a generic pipeline descriptor > with a format like: > > [pipeline pipe1] > link0 = SGRBG10 640x480: entity1:0 -> entity2:0[1] > link1 = SGRBG10 640x480: entity2:2-> entity3:0[1] > link2 = UYVY 640x480: entity3:1-> entity4:0[1] > link3 = UYVY 640x480: entity4:1-> entity5:0[1] > > sink0 = UYVY 320x200: entity5:0[1] > sink1 = UYVY 640x480: entity3:0[1] Well, first, this looks like very unsuitable for key=value file. Plus, it will not be easy to parse. .... and control map needs to be per-pipeline-configuration. Again, proposed Windows-style format can not easily do that. Best regards, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Attachment:
signature.asc
Description: Digital signature
