Re: please help ..The New DDE_USB is giving compilation errors...
Hi I have tried both usb mouse and usb camera. 1) For usb camera a dope has started and a small menu has came showing "usbcam" and "exit". But it is not showing anything when I am clicking on usbcam. Here is the menu.lst that I have used for webcam : title usbcam kernel /home/tapas/10AprilUserbuild/bin/x86_586/bootstrap -modaddr 0x04000000 module /home/tapas/8thAprilKernel/fiasco -nokdb -nowait module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/sigma0 module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/roottask module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/log module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/names module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/dm_phys module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/l4io module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/l4dope --l4io module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/usbcore module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/usbcam vbeset 0x117 506070 2) For usbhid , we have connected a usb mouse . But it was not working. Here is the menu.lst , I have used for usb mouse. title usbhid kernel /home/tapas/10AprilUserbuild/bin/x86_586/bootstrap -modaddr 0x04000000 module /home/tapas/8thAprilKernel/fiasco -nokdb -nowait module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/sigma0 module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/roottask module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/log module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/names module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/dm_phys module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/l4io module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/l4dope --l4io module /home/tapas/10AprilUserbuild/bin/x86_586/l4v2/usbhid vbeset 0x117 506070 Please know that we have a plan to add support for new webcams . Please let us know following information : 1) Please provide us the menu.lst which you have used for usbcam and usbhid. 2) I have found following files under directory "/home/tapas/10AprilUserbuild/source/pkg/usb/examples/usbcam/src" main.c , support.c , usbcam.c and libv4lconvert (directory) It seems to me to add support for a new webcam , we need to modify only usbcam.c . Please let us know this . It will be great if you can provide documentation for libv4lconvert and your usbcam driver. On Fri, Apr 10, 2009 at 1:59 PM, Dirk Vogt <dvogt@os.inf.tu-dresden.de> wrote:
Hi Again, Sorry there seems one line to be missing which is needed to switch into graphical mode.
title usbcam kernel /boot/bootstrap modaddr 0x02000000 module /boot/fiasco -nokdb -nowait module /boot/sigma0 module /boot/roottask module /boot/log module /boot/names module /boot/dm_phys module /boot/l4io module /boot/dope module /boot/usbcore module /boot/usbcam vbeset 0x117
Ciao, Dirk.
Hi,
1) For usb camera a dope has started and a small menu has came showing "usbcam" and "exit". But it is not showing anything when I am clicking on usbcam.
That's the normal behavior of usbcam, when it does not find a usbcam. However you should see in the debugging console that usbcore and have usbcam are initialized. When usbcam recognizes a new cam, a new button video0 will appear. By clicking this button usbcam will start the video capture.
2) For usbhid , we have connected a usb mouse . But it was not working. Here is the menu.lst , I have used for usb mouse.
It seems you forgot to put usbcore into your menu.lst. Remember, DDEUSB uses a client/server approach to offer USB functionality. The usbcore is the only one to touch the host-controller hardware and thus needed for all other USB drivers.
Please know that we have a plan to add support for new webcams . Please let us know following information :
1) Please provide us the menu.lst which you have used for usbcam and usbhid.
They do not differ much from yours.
2) I have found following files under directory "/home/tapas/10AprilUserbuild/source/pkg/usb/examples/usbcam/src" main.c , support.c , usbcam.c and libv4lconvert (directory)
Actually usbcam.c is just containing the gui and the v4l and v4l2 capturing code. The first should be documented somewhere in the dope package and for the second there is plenty of documentation including small examples spread all over the world wide web. the libv4lconvert was taken from libv4l [1] and was needed to convert the data from the video device from e.g. jpeg to the vscreen's pixel format. Further, support.c implements some functions the were needed by linux kernel part of V4L. If you have a look at the makefile, you can probably see how to add support for new usbcams. Good luck, Dirk. [1] http://freshmeat.net/projects/libv4l
participants (2)
-
Dirk Vogt -
tapas kundu