On Mon, 2007-11-19 at 15:30 -0800, David Sharp wrote: > [+list. Jon: please use Reply To All when replying] > > On Nov 19, 2007 10:18 AM, Jon Legarrea <[EMAIL PROTECTED]> wrote: > > > > On Wed, 2007-11-14 at 22:01 -0800, David Sharp wrote: > > > On Nov 14, 2007 8:37 AM, Jon Legarrea <[EMAIL PROTECTED]> wrote: > > > > Hello, i trying to use the trunk version, but it don't insert the > > > > module, is first time i try to use this module > > > > > > > > > > > > also i want to try to help development, actually i am in a class they > > > > are teaching about system calls and now module programming, i want to > > > > if is possible, understand how it works everythink and do a small > > > > subtask, easy or medium level. > > > > > > I think something you could do that would be pretty self contained > > > would be to port the driver to use the usbvideo module. I've been > > > wanting to do this myself, but I haven't found the time. Only issues I > > > see would be understanding how to interact with the devices, which is > > > hard when there is little to no documentation. I would suggest working > > > in a branch and getting it to work with just one device that you can > > > test with. > > > > Yeah, can be, but I don't know how to start, do you have some > > information about how to port to usbvideo module or were i can find it? > > I would just look at existing drivers that use usbvideo, such as all > the drivers in the usbvideo dir [1]. Although, now that I look at it, > those drivers are all really old, and the linux-uvc project is not > using it. This makes me wonder if this is really such a good idea. In > any case, it would be nice to solidify our v4l2 interface, since at > the moment it is very sensitive to what program is used.
I have a look of the v4l2 API, but after I release that there is already and implementation of v4l2 in m5602-ov9650-2 and m5603c-mt9v011 branches, so, how can i solidify v4l2 interface? > > http://lxr.linux.no is very handy, if you didn't know about it. yeah > > Others will have to reply to the rest. > > [1] http://lxr.linux.no/source/drivers/media/video/usbvideo/ > > > i try all the modules, the m5602-ov9650-2 works but not in xawtv, i > > explain that. > > > > i can load the module so dmesg says: > > > > Linux video capture interface: v2.00 > > /usr/src/m5602-ov9650-2/m5602.c: usb_m5602_init - WebCam driver startup > > /usr/src/m5602-ov9650-2/m5602.c: BisonCam webcam found. > > /usr/src/m5602-ov9650-2/m5602.c: [usb_m5602_probe:871] cam ee786000 > > /usr/src/m5602-ov9650-2/m5602.c: [m5602_initialize_camera:253] > > m5602_initialize_camera > > /usr/src/m5602-ov9650-2/m5602.c: m5602_probe - m5602 WebCam driver is > > now controlling video device 0 > > usbcore: registered new interface driver m5602 > > /usr/src/m5602-ov9650-2/m5602.c: 0.1.0:M5602 Webcam Driver > > > > > > > > when I do, "xawtv -hwscan" it says: > > > > This is xawtv-3.95.dfsg.1, running on Linux/i686 (2.6.22-3-686) > > looking for available devices > > /dev/video0: OK [ -device /dev/video0 ] > > type : v4l2 > > name : BisonCam > > flags: capture > > > > > > > > > > > > after there is a black screen, just the webcam have the green ligth, but > > xawtv don't show nothing, someone know, i have after open xawtv that one > > in dmesg: > > > > /usr/src/m5602-ov9650-2/m5602_v4l2.c: m5602 open > > /usr/src/m5602-ov9650-2/m5602_v4l2.c: m5602 open > > /usr/src/m5602-ov9650-2/m5602_v4l2.c: m5602 open > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 2dba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 80ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 2cba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 80ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 09ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 80ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 35ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 80ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 35ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602.c: [read_sensor_register:69] read register > > 80ba result 01 value ff > > /usr/src/m5602-ov9650-2/m5602_v4l2.c: m5602 open > > /usr/src/m5602-ov9650-2/m5602_v4l2.c: m5602 open > > /usr/src/m5602-ov9650-2/m5602_v4l2.c: m5602 open > > > > > > it's like it is working but the program don't take it or ??? > > > > > > thank you > > > > > > Here's a quote from an earlier mail I sent on the subject, on > > > September 18 if you want to find the thread in the archives: > > > > > > On Sep 18, 2007 6:34 PM, David Sharp <[EMAIL PROTECTED]> wrote: > > > > actually, I'd like to rewrite the driver to use usbvideo > > > > (drivers/media/video/usbvideo), which implements the entire v4l2 > > > > access layer, leaving our driver to implement just the hardware > > > > access. I haven't actually looked to see if this is doable, but it > > > > seems like a good idea. We would have a lot less code to implement and > > > > then maintain. > > -- > > http://korea.trastear.com/ > > > > no es rico aquel que tiene mucho, sino el que es feliz con lo que tiene > > asko daukana ez da benetan aberatsa, daukanarekin zoriontsua dena da > > aberatsena > > > > Un saludo. / Agur bero bat. > > > > Jon Legarrea Oteiza > > > > -- http://korea.trastear.com/ no es rico aquel que tiene mucho, sino el que es feliz con lo que tiene asko daukana ez da benetan aberatsa, daukanarekin zoriontsua dena da aberatsena Un saludo. / Agur bero bat. Jon Legarrea Oteiza ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ M560x-driver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
