On Thu, 5 Mar 2009, Hans Verkuil wrote:
> Reserved bits are there for a reason. If a particular bit of information
> it a perfect match with for that API, then it seems utterly pointless to
> me to decide not to use them 'just because we might run out in the
> future'.
It would be one thing if the
> On Thu, 5 Mar 2009, Hans Verkuil wrote:
>>
>> ENUMINPUT is probably a better solution: you can say something like
>> "Camera 1 (sensor1)", "Camera 2 (sensor2)".
>>
>> It remains a bit of a hack, though.
>
> Maybe use some of the reserved bits in v4l2_input to show not only the
> sensor orientati
On Thu, 5 Mar 2009, Hans Verkuil wrote:
>
> ENUMINPUT is probably a better solution: you can say something like
> "Camera 1 (sensor1)", "Camera 2 (sensor2)".
>
> It remains a bit of a hack, though.
Maybe use some of the reserved bits in v4l2_input to show not only the
sensor orientation, but also
On Thu, 5 Mar 2009, Tuukka.O Toivonen wrote:
> On Wednesday 04 March 2009 16:52:20 ext Hans Verkuil wrote:
> > > Alternatively, VIDIOC_QUERYCAP could be used to identify the sensor.
> > > Would it make more sense if it would return something like
> > > capability.card: `omap3/smia-sensor-12-1234
> On Wednesday 04 March 2009 16:52:20 ext Hans Verkuil wrote:
>> > Alternatively, VIDIOC_QUERYCAP could be used to identify the sensor.
>> > Would it make more sense if it would return something like
>> > capability.card: `omap3/smia-sensor-12-1234-5678//'
>> > where 12 would be manufacturer_id
On Wednesday 04 March 2009 16:52:20 ext Hans Verkuil wrote:
> > Alternatively, VIDIOC_QUERYCAP could be used to identify the sensor.
> > Would it make more sense if it would return something like
> > capability.card: `omap3/smia-sensor-12-1234-5678//'
> > where 12 would be manufacturer_id, 1234
Hi tuukka,
Chip identification could be used for many other camera devices. Not
only for SMIA compatible sensors.
It could be used for generic camera devices I guess for any other
reasons, like checking chip version on factory assembly line in mass
production.
Something like G_CHIP_IDENT (as Hans
On Wed, 4 Mar 2009, ribrishimov wrote:
> I am planning to export the chip identification information
> to user space using VIDIOC_DBG_G_CHIP_IDENT.
> Here's a sketch:
> #define V4L2_IDENT_SMIA_BASE(0x53 << 24)
> then in sensor driver's VIDIOC_DBG_G_CHIP_IDENT ioctl handler:
> struct v4l
Hi Tuukka,
> Hi,
>
> I am writing a generic driver for SMIA-compatible sensors.
> SMIA-sensors have registers containing:
> u16 model_id
> u16 revision_number
> u8 manufacturer_id
> which could be used to detect the sensor.
> However, since the driver is generic, it is not interested
> of th
...@ok.research.nokia.com] On Behalf Of Tuukka.O Toivonen
Sent: Wednesday, March 04, 2009 4:13 PM
To: ext Hans Verkuil
Cc: cam...@ok.research.nokia.com; linux-media@vger.kernel.org
Subject: [Camera] identifying camera sensor
Hi,
I am writing a generic driver for SMIA-compatible sensors.
SMIA-sensors have registers
Hi,
I am writing a generic driver for SMIA-compatible sensors.
SMIA-sensors have registers containing:
u16 model_id
u16 revision_number
u8 manufacturer_id
which could be used to detect the sensor.
However, since the driver is generic, it is not interested
of these values.
Nevertheless, in s
11 matches
Mail list logo
