Re: [M560x-driver-support] What do the developers use for development?

[Ivan Vucica <ivucica@gm...>]

Thanks for the response!

Here are some of the notes from my experiences with that branch. I'm sorry 
for being ignorant on how to produce patches that might be easier for 
you to use.

1) Kernel 2.6.22 no longer includes file linux/usb_ch9.h, now it's called 
linux/usb/ch9.h.
I changed the include appropriately.
2) Changed the device definitions as here:
////////CUT
static struct usb_device_id m5603c_table[] = {
         {USB_DEVICE(0x0458, 0x7020)},
     {USB_DEVICE(0x041e, 0x4038)},
     {USB_DEVICE(0x0402, 0x5603)},
     {}
};

static char* m5603c_name[4] = {
     "Genius Slim 321C",
     "Creative WebCam Live! Pro",
     "Sweex",
     NULL
};
/////////CUT

I did not study the code below, but is the name in the m5603c_name array 
supposed to match whatever the device reports? (Currently, lsusb seems to 
be playing tricks on me, and /proc/bus/usb/devices seems to report name of 
"For demo only", which seems right to me since I saw that somewhere, too, 
but not in the lsusb listing).

3) Test program for sweex 5603 needs modification in pusb-linux.h. At 
beginning add:
///// CUT
#define BITS_PER_LONG 32
#include <linux/types.h>
///// CUT
Looks like they added an #ifdef __KERNEL__, that's why this is needed.
4) Same test program, pusb-linux.c in line 285 change ctrl.bRequesttype 
into ctrl.bRequestType. In Makefile, in line 8, remove -DFC5.

Images that were generated seem to have only 0x0a0a0a color. When I ran it 
later on, it appears to have frozen somewhere.

5) Driver only generates blank picture, too.
6) $ insmod m5603c DBUG=16
m5603c: Unknown parameter `DBUG'

I also tried with DBG and DEBUG.

7) I did experience some null pointer related errors, but they appear to 
be gone now. (I don't know what I did, I'll inform you if they 
resurface.)


Hopefully some of this helps!

------------
Ivan Vucica


On Thu, 30 Aug 2007, Willem Duinker wrote:

>
> You can use the m5603c-mtv011 branch (under branches in the svn). Add the 
> sweex id to the device-table (line 38 in m5603c.c)
>
> and it should work with the LiveCam program (see sourceforge). The is was 
> made with a similar camera.
>
> Do not forget to put the firmware in the right directory
>
> The main trunk should also work (with the firmware and start-up scripts in 
> right place, check with dmesg after loading the driver with DBUG=16) for the 
> sweex. It only does always start (a bug in the start-up code)
> You should be able to compare with the above-mentioned branch.
>
> Willem
>

Re: [M560x-driver-support] What do the developers use for development?

[Willem Duinker <wduinker@xs...>]

Ivan Vucica wrote:

>Hi,
>
>I'm wondering what do the current driver developers use as their 
>development software configuration, since it might be the key to my lack 
>of success in getting the Sweex cam to work. It's the 0402:5603 piece of 
>hardware. The driver detects mt9v001 sensor and mentions ID 82 32, however 
>  
>

You can use the m5603c-mtv011 branch (under branches in the svn). Add 
the sweex id to the device-table (line 38 in m5603c.c)

and it should work with the LiveCam program (see sourceforge). The is 
was made with a similar camera.

Do not forget to put the firmware in the right directory

The main trunk should also work (with the firmware and start-up scripts 
in right place, check with dmesg after loading the driver with DBUG=16) 
for the sweex. It only does always start (a bug in the start-up code)
You should be able to compare with the above-mentioned branch.

Willem

>no program is able to get any kind of picture from the camera, including 
>"xawtv" with -f option, as suggested in the documentation.
>
>With "hasciicam", I get "error in VIDIOCGCAP: invalid argument". I have 
>tried specifying the image size manually (with -s 640x480). Most other 
>programs have similar problems.
>
>Is Debian GNU/Linux, kernel 2.6.22 supported, or at least 2.6.21? I have 
>been unable to get image with any of these two kernels.
>
>Any help would be appreciated. Shell access to my laptop can be 
>arranged (to a limited amount of time, however, since I am on dialup). If 
>necessary, VNC access can be set up, too. If you supply what information I 
>should submit, I will give it out. Since I have "some" programming 
>experience, with proper directions I might try to fix the bug, but since I 
>am not familiar with the API I do not know where to start.
>
>If possible, I'd appreciate some response to acknowledge this message.
>
>------------
>Ivan Vucica
>
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc.
>Still grepping through log files to find problems?  Stop.
>Now Search log events and configuration files using AJAX and a browser.
>Download your FREE copy of Splunk now >>  http://get.splunk.com/
>_______________________________________________
>M560x-driver-support mailing list
>M560x-driver-support@...
>https://lists.sourceforge.net/lists/listinfo/m560x-driver-support
>
>
>  
>

[M560x-driver-support] What do the developers use for development?

[Ivan Vucica <ivucica@gm...>]

Hi,

I'm wondering what do the current driver developers use as their 
development software configuration, since it might be the key to my lack 
of success in getting the Sweex cam to work. It's the 0402:5603 piece of 
hardware. The driver detects mt9v001 sensor and mentions ID 82 32, however 
no program is able to get any kind of picture from the camera, including 
"xawtv" with -f option, as suggested in the documentation.

With "hasciicam", I get "error in VIDIOCGCAP: invalid argument". I have 
tried specifying the image size manually (with -s 640x480). Most other 
programs have similar problems.

Is Debian GNU/Linux, kernel 2.6.22 supported, or at least 2.6.21? I have 
been unable to get image with any of these two kernels.

Any help would be appreciated. Shell access to my laptop can be 
arranged (to a limited amount of time, however, since I am on dialup). If 
necessary, VNC access can be set up, too. If you supply what information I 
should submit, I will give it out. Since I have "some" programming 
experience, with proper directions I might try to fix the bug, but since I 
am not familiar with the API I do not know where to start.

If possible, I'd appreciate some response to acknowledge this message.

------------
Ivan Vucica

[M560x-driver-support] insmod dmesg output

[Guido Sanchez <sanchez.guido@gm...>]

Hi. Recently I have tried to install m560x.ko and I got this dmesg output.

I am using debian testing. First I modprobed videodev and v4l1-compat,
then I copied the firmware files in fw to /lib/firmware. The output of
dmesg is this, hope it is useful.

Linux video capture interface: v2.00
/home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c:
usb_m560x_init - M560x-based WebCam driver startup
/home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c:
m560x_probe - M560x-based WebCam connected
/home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_mt9v111.c:
[m5602_probe_mt9v111:189] probe mt9v111 sensor id ff ff
/home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_ov9650.c:
[m5602_probe_ov9650:190] probe ov9650 sensor id ff ff
/home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m5602_ov7640.c:
[m5602_probe_ov7640:190] probe ov7640 sensor id ff ff
Unable to handle kernel NULL pointer dereference at 0000000000000068 RIP:
 [<ffffffff884aeee1>] :m560x:usb_m560x_probe+0x37e/0x682
PGD 33af067 PUD 2cae067 PMD 0
Oops: 0000 [1] SMP
CPU 0
Modules linked in: m560x videodev v4l2_common v4l1_compat usbhid hid
fglrx(P) binfmt_misc rfcomm l2cap bluetooth ppdev parport_pc lp
parport button ac battery ipv6 cpufreq_stats cpufreq_conservative
cpufreq_powersave cpufreq_ondemand dm_crypt dm_snapshot dm_mirror
dm_mod powernow_k8 freq_table cpufreq_userspace loop pcmcia
firmware_class wlan_scan_sta snd_hda_intel ath_rate_sample i2c_piix4
snd_hda_codec joydev snd_pcm_oss snd_mixer_oss tsdev sdhci ath_pci
i2c_core mmc_core yenta_socket rsrc_nonstatic shpchp wlan snd_pcm
pcmcia_core pci_hotplug ath_hal(P) snd_timer pcspkr psmouse k8temp
serio_raw snd soundcore snd_page_alloc evdev ext3 jbd mbcache ide_cd
cdrom sd_mod ata_generic sata_sil libata scsi_mod atiixp 8139too
generic 8139cp mii ide_core ehci_hcd ohci_hcd thermal processor fan
Pid: 11872, comm: insmod Tainted: P       2.6.21-2-amd64 #1
RIP: 0010:[<ffffffff884aeee1>]  [<ffffffff884aeee1>]
:m560x:usb_m560x_probe+0x37e/0x682
RSP: 0018:ffff810002a0fc98  EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff810002a16000 RCX: ffff8100026e55b8
RDX: ffff8100026e5238 RSI: ffff8100026e5190 RDI: ffff810002a16000
RBP: 0000000000000003 R08: 0000000000000124 R09: 0000000000000000
R10: 00000000047c8b30 R11: ffffffff8026c234 R12: ffffffff884b5e00
R13: ffff8100379dc000 R14: 0000000000000000 R15: ffff81003595b000
FS:  00002b373886e6e0(0000) GS:ffffffff804d7000(0000) knlGS:00000000f75eda20
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000068 CR3: 0000000002e7b000 CR4: 00000000000006e0
Process insmod (pid: 11872, threadinfo ffff810002a0e000, task ffff810027f158d0)
Stack:  0000000000000282 ffff81003595b5d0 ffff81003595b088 ffff8100379dc000
 0000000000000001 ffff810002a17dd0 ffff81003595b000 ffff81003595b088
 0000000000000001 ffff8100379dc020 0000000000000000 ffffffff884b5e00
Call Trace:
 [<ffffffff8037ef6b>] usb_probe_interface+0xa7/0xde
 [<ffffffff803716e0>] really_probe+0xc5/0x14a
 [<ffffffff80371899>] __driver_attach+0x0/0x93
 [<ffffffff803718f3>] __driver_attach+0x5a/0x93
 [<ffffffff80370bd4>] bus_for_each_dev+0x43/0x6e
 [<ffffffff80370f16>] bus_add_driver+0x6b/0x18d
 [<ffffffff8037ea78>] usb_register_driver+0x7e/0xe4
 [<ffffffff8801d030>] :m560x:usb_m560x_init+0x30/0x66
 [<ffffffff802947c4>] sys_init_module+0x1656/0x17b9
 [<ffffffff8020ca90>] dput+0x32/0x150
 [<ffffffff8025511e>] system_call+0x7e/0x83


Code: 41 ff 56 68 f6 05 14 e2 00 00 10 74 39 41 b9 44 00 00 00 41
RIP  [<ffffffff884aeee1>] :m560x:usb_m560x_probe+0x37e/0x682
 RSP <ffff810002a0fc98>
CR2: 0000000000000068
/home/guiss/dev/m560x-driver/m560x/trunk/km_m560x/m560x_core.c: m560x open


Greetings,

Guido Sanchez
-- 
Never make any mistaeks.

[M560x-driver-support] module m560x didn't compile

[Ludovic Lestang <ludovic.lestang@ne...>]

Hi every body

First i'm french so excuse my poor english.

I tried to compile this module for my asuslaptop A7D from the svn
sources in the driver and branches directory.
I give you the output from 'make' in /branches/m5602-ov9650 because is
shortly :

> make -C /lib/modules/2.6.22.3-ccj53-default/build
> SUBDIRS=/home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650
> modules
> make[1]: Entering directory
> `/usr/src/linux-2.6.22.3-ccj53-obj/i386/default'
> make -C ../../../linux-2.6.22.3-ccj53
> O=../linux-2.6.22.3-ccj53-obj/i386/default modules
> CC [M]
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.o
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:
> In function ‘ov9650_i2c_write’:
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:28:
> error: implicit declaration of function ‘write_m5602_sensor_register’
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:
> In function ‘ov9650_set_ctrl’:
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:64:
> warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from
> integer without a cast
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:65:
> warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from
> integer without a cast
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:68:
> warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from
> integer without a cast
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:71:
> warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from
> integer without a cast
> /home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.c:74:
> warning: passing argument 3 of ‘ov9650_i2c_write’ makes pointer from
> integer without a cast
> make[4]: ***
> [/home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650/m5602_ov9650.o]
> Error 1
> make[3]: ***
> [_module_/home/ludo/Documents/Utils/webcam/m560x-driver/m560x/branches/m5602-ov9650]
> Error 2
> make[2]: *** [modules] Error 2
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory
> `/usr/src/linux-2.6.22.3-ccj53-obj/i386/default'
> make: *** [all] Error 2

I'm using opensuse 10.2 whith kernel 2.6.22.3 with kernel sources
installed and linux-kernel-headers 2.6.22.10

Thanks a lot for you help

Regards
Ludo