Hi Martin, I'm not an expert of V4L2 and this camera sensor, too. But, if you don't mind, I want to leave some comments about the registers, and I hope that it helps you. 2011-05-30 ìí 9:07, Martin Strubel ì ê: > Hi Hans, > >> >> Can you give examples of the sort of things that are in those registers? >> Is that XML file available somewhere? Are there public datasheets? >> > > If you mean the sensor datasheets, many of them are buried behind NDAs, > but people are writing opensourced headers too...let's leave this to the > lawyers. > > Here's an example: http://section5.ch/downloads/mt9d111.xml > The XSLT sheets to generate code from it are found in the netpp > distribution, see http://www.section5.ch/netpp. You might have to read > some of the documentation to get to the actual clues. As you said, obviously this camera has a lot of registers. But, IMHO, even it can be expressed by one subdev driver like any other ones. Almost registers can be absorbed and adapted at the start(or booting) time. And the most others also can be defined at the current V4L2 APIs. (like controls, croppings, buffers, powers, etc) The matter is to find which factor can vary, when the camera setting is varied by the board as you said. And in just my short thinking, this is not much to catch. If there are such things, not expressed using current V4L2 APIs, but needed for your works or your board, you can submit this APIs to ML. The best thing is, you collect such things(it can be express current V4L2 APIs), and submit new V4L2 APIs, because there are many other people handling camera driver like you, and they can think similary like you. For sure, they can welcome to birth new APIs. Cheers, Heungjun Kim -- 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
