Hi Ilyes,

Thank you verry much for your work. I would like to provide you such  
trace, but I don't know how to change brightness, saturation or anything  
else. I didn't find in My computer->BisonCam anything to change except  
color management in properties (but it's only possible to load icc/icm  
file); and I didn't find any other application for the webcam whith those  
functions.



On Wed, 14 May 2008 10:11:22 +0200, Ilyes Gouta <[EMAIL PROTECTED]>  
wrote:

> Hi again :)
>
> You have an OV7640 sensor attached to your m5603c bridge. :) I
> couldn't see it last night, it was too late...
>
> From the converted trace, line 1770:
>
> unsigned char buffer[1] = { 0x21, };
> memcpy(kbuff, buffer, sizeof(buffer)); /* kbuff == cam->control_buffer */
> usb_control_msg(udev, usb_sndctrlpipe(udev, 0), 0x04, 0x40, 0x17,
> 0x7642, kbuff, 1, 100);
>
> 0x42 is the slave address of the sensor. I'm still interested in the
> complete trace.
>
> BR,
> Ilyes Gouta.
>
> On Wed, May 14, 2008 at 9:56 AM, Ilyes Gouta <[EMAIL PROTECTED]>  
> wrote:
>> Hi Petr,
>>
>> I parsed the trace you sent to me yesterday and unfortunately I wasn't
>> able to find any communication directed toward the sensor so that I
>> can identify it. Generally when the drivers wants to send a parameter
>> to the sensor, it includes its slave address within the message. This
>> allows us to identify it. You'll find attached the converted .c file
>> that reproduces all the communication captured in the usbsnoop trace.
>> Attached too is the Python script I wrote to retrieve the
>> initialization sequence for the 5602 and 5603c bridges.
>>
>> I'd like to ask you if you can provide me with another trace where you
>> actually change the brightness, gain, color saturation, etc. while
>> usbsnoop is capturing the USB traffic on Windows. We'll have a better
>> chance to identify the sensor.
>>
>> BR,
>> Ilyes Gouta.
>>
>> On Tue, May 13, 2008 at 4:38 PM, Ilyes Gouta <[EMAIL PROTECTED]>  
>> wrote:
>>> Perfect!
>>>
>>> Thanks Petr, I'll have a look on this asap.
>>>
>>> BR,
>>> Ilyes Gouta.
>>>
>>> 2008/5/13 Petr Dlouhý <[EMAIL PROTECTED]>:
>>>> The text of the last email should be:
>>>>  Hi,
>>>>
>>>>  I had to shrink the partition and install XP (I get only gray square  
>>>> instead of picture in VirtualBox). Here is the log.
>>>>
>>>> > Hi,
>>>>  >
>>>>  > Yes you're right Petr. The driver is USB 2.0 only. The cam requires
>>>>  > another initialization sequence if it's on USB 1.1.
>>>>  >
>>>>  > Do you have Windows installed? Can you provide us with USB traces  
>>>> for
>>>>  > the cam initialization sequence and data exchange? You can do that
>>>>  > using sniffusb.exe/usbsnoop.
>>>>  > (http://benoit.papillault.free.fr/usbsnoop/sniff-bin-1.8.zip) We  
>>>> can
>>>>  > then determine your sensor and eventually write some code to  
>>>> support
>>>>  > it.
>>>>  >
>>>>  > BR,
>>>>  > Ilyes Gouta.
>>>>  >
>>>>
>>>>
>>>>
>>>>
>>>> Petr Dlouhý
>>>>  [EMAIL PROTECTED]
>>>>
>>>
>>



-- 
Petr Dlouhý

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
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

Reply via email to