Skip to contentSkip to conversation

New v4l2 driver for atmel boards

DISCUSSION Sedji Gaouaou 3 participants 5 messages Feb 18, 2009 – Feb 19, 2009 Media (V4L/DVB)

lore
Share & tools
lore
#1 lore raw

(moved to the new v4l list)

Quoted 6 lines · Sedji Gaouaou

Hi everybody,

I am writing here to know if it is the proper place to send a driver that I have written for atmel's boards.
I would like to know as well if there is a git tree against which I should based my patch or should I based it against the latest rc?

Hi Sedji,

what hardware is it for? avr32 or at91 (ARM)? And what API are you using to communicate with sensors? Currently there are two APIs in the kernel - int-device and soc-camera, and they both should at some point (soon) converge to the new "V4L2 driver framework." They all have (one of) the goal(s) to reuse sensor (or whatever subdevice) drivers with various hosts. Which of them are you using?

I've recently got test hardware from Atmel for an AP7000 board (NGW100), and was planning to convert the existing external ISI driver from Atmel to the soc-camera API, but I have no idea when I find time for that.

As for against which tree to submit patches, I think,
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git should be a good starting point.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer

#2 lore raw

Hi Guennadi,

Quoted 1 line

what hardware is it for? avr32 or at91 (ARM)?

I am working on AT91(ARM).
And what API are you using

Quoted 1 line

to communicate with sensors?

I am using the ISI IP.
Currently there are two APIs in the kernel -

Quoted 4 lines

int-device and soc-camera, and they both should at some point (soon) converge to the new "V4L2 driver framework." They all have (one of) the goal(s) to reuse sensor (or whatever subdevice) drivers with various hosts. Which of them are you using?

I've recently got test hardware from Atmel for an AP7000 board (NGW100), and was planning to convert the existing external ISI driver from Atmel to the soc-camera API, but I have no idea when I find time for that.

I have a driver which is not using the soc-camera layer...
Which driver is currently using this soc-camera layer so I can have a look at it and maybe I could try to convert mine.

Regards,
Sedji

#3 lore raw
Quoted 13 lines · Sedji Gaouaou

Hi Guennadi,

Quoted 1 line

what hardware is it for? avr32 or at91 (ARM)?

I am working on AT91(ARM).
And what API are you using

Quoted 1 line

to communicate with sensors?

I am using the ISI IP.
Currently there are two APIs in the kernel -

Quoted 5 lines

int-device and soc-camera, and they both should at some point (soon) converge to the new "V4L2 driver framework." They all have (one of) the goal(s) to reuse sensor (or whatever subdevice) drivers with various hosts. Which of them are you using?

Quoted 8 lines
Quoted 4 lines

I've recently got test hardware from Atmel for an AP7000 board (NGW100), and was planning to convert the existing external ISI driver from Atmel to the soc-camera API, but I have no idea when I find time for that.

I have a driver which is not using the soc-camera layer...
Which driver is currently using this soc-camera layer so I can have a look at it and maybe I could try to convert mine.

That would be great. You can look at

drivers/media/video/pxa_camera.c
drivers/media/video/sh_mobile_ceu_camera.c

and, if you wait for my pool request, expected later today, and pull from the mercurial tree, also at

drivers/media/video/mx3_camera.c

but, even the former two should be enough for you to start with.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer