Ilyes
I have to clean up the code and try to get my two cameras to work as
well. Probably not before next weekend.
Yes, there is a different init sequence. I have not tried to switch over
while capturing.
Willem
Ilyes Gouta wrote:
> Hi Willem,
>
> Thanks for the link. Is it possible to release your test programs so
> that I can integrate this new feature into the V4L2 capable m5603c
> kernel driver?
>
> Willem, does the bridge/sensor require a special initialization to
> toggle on the YCrCb/JPEG mode? Do you have such an init. sequence in
> your test programs?
>
> Regards,
> Ilyes Gouta.
>
> On Sun, Sep 28, 2008 at 1:44 PM, wduinker <[EMAIL PROTECTED]> wrote:
>
>> Sorry document is
>>
>> www.w3.org/Graphics/*JPEG*/itu-t81.pdf
>>
>> The binary decoding tables in the windows driver for the DC table are as
>> below. Once I knew what they should look like I was able to find them in the
>> windows driver. You can do a binary search in the .sys file of the windows
>> driver. The AC table has a separate run and seperate size table, next to the
>> maxcode, valptr and mincode
>>
>>
>> entry-number, maxcode, valcode, mincode
>>
>> 0 ffffffff 0000 00000000 1 00000000 0000 00000000 2 00000006 0001
>> 00000002 3 0000000e 0006 0000000e 4 0000001e 0007 0000001e 5 0000003e
>> 0008 0000003e 6 0000007e 0009 0000007e 7 000000fe 000a 000000fe 8
>> 000001fe 000b 000001fe 9 000003fe 000c 000003fe 10 ffffffff 0000
>> 00000000 11 ffffffff 0000 00000000 12 ffffffff 0000 00000000 13
>> ffffffff 0000 00000000 14 ffffffff 0000 00000000 15 ffffffff 0000
>> 00000000 16 ffffffff 0000 00000000
>>
>>
>> Ilyes Gouta wrote:
>>
>>> Willem,
>>>
>>> Where can we find TO81e.doc? Can you post the test programs and some
>>> sample code? I'm really thrilled to get this code working on my
>>> mt9v011/m5603c combo.
>>>
>>> Regards,
>>> Ilyes Gouta.
>>>
>>> On Sat, Sep 27, 2008 at 9:00 PM, wduinker <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>> To all m5603c users
>>>>
>>>> This summer I have worked again on the m5603c.
>>>>
>>>> I finally figured out the huffman tables for the jpeg. The tables below
>>>> give the same decoding tables that are in the windows drivers. Decoding
>>>> tables in the windows driver are mincode, maxcode and valptr (Figure
>>>> F.15 page 108 TO81e.doc). The DC is non standard. It does not have the
>>>> "1" as category value. The AC tables is standard. Tables are used as far
>>>> as I see for Y, Cb and CR.
>>>>
>>>> I test it with the test-pattern from the mt9v011 sensor. I have a user
>>>> space program with reads the data from the usbfs system. Works just as
>>>> fast as the kernel driver.
>>>>
>>>> There is still something wrong with the quality tables and maybe the
>>>> header settings. I am producing both 4:2:2 as well as 4:1:1 jpeg raw
>>>> data files.
>>>>
>>>> DC table
>>>> unsigned char dht1[] =
>>>> { 0xff,0xc4,0x00,0x1f, 0x00};
>>>> unsigned char bitsYDC[] =
>>>> {0, 1, 5, 1, 1, 1, 1 , 1, 1, 0, 0, 0, 0, 0, 0, 0, 0};
>>>> unsigned char valYDC[] = {0, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12};
>>>>
>>>> AC table
>>>>
>>>> unsigned char dht2[] =
>>>> { 0xff,0xc4,0x00,0xb5, 0x10};
>>>> unsigned char bitsYAC[] =
>>>> {0, 2, 1, 3, 3, 2, 4, 3, 5, 5, 4, 4, 0, 0, 1, 0x7d};
>>>> unsigned char valYAC[] =
>>>> { 0x01, 0x02, 0x03, 0x00, 0x04, 0x11, 0x05, 0x12,
>>>> 0x21, 0x31, 0x41, 0x06, 0x13, 0x51, 0x61, 0x07,
>>>> 0x22, 0x71, 0x14, 0x32, 0x81, 0x91, 0xa1, 0x08,
>>>> 0x23, 0x42, 0xb1, 0xc1, 0x15, 0x52, 0xd1, 0xf0,
>>>> 0x24, 0x33, 0x62, 0x72, 0x82, 0x09, 0x0a, 0x16,
>>>> 0x17, 0x18, 0x19, 0x1a, 0x25, 0x26, 0x27, 0x28,
>>>> 0x29, 0x2a, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39,
>>>> 0x3a, 0x43, 0x44, 0x45, 0x46, 0x47, 0x48, 0x49,
>>>> 0x4a, 0x53, 0x54, 0x55, 0x56, 0x57, 0x58, 0x59,
>>>> 0x5a, 0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69,
>>>> 0x6a, 0x73, 0x74, 0x75, 0x76, 0x77, 0x78, 0x79,
>>>> 0x7a, 0x83, 0x84, 0x85, 0x86, 0x87, 0x88, 0x89,
>>>> 0x8a, 0x92, 0x93, 0x94, 0x95, 0x96, 0x97, 0x98,
>>>> 0x99, 0x9a, 0xa2, 0xa3, 0xa4, 0xa5, 0xa6, 0xa7,
>>>> 0xa8, 0xa9, 0xaa, 0xb2, 0xb3, 0xb4, 0xb5, 0xb6,
>>>> 0xb7, 0xb8, 0xb9, 0xba, 0xc2, 0xc3, 0xc4, 0xc5,
>>>> 0xc6, 0xc7, 0xc8, 0xc9, 0xca, 0xd2, 0xd3, 0xd4,
>>>> 0xd5, 0xd6, 0xd7, 0xd8, 0xd9, 0xda, 0xe1, 0xe2,
>>>> 0xe3, 0xe4, 0xe5, 0xe6, 0xe7, 0xe8, 0xe9, 0xea,
>>>> 0xf1, 0xf2, 0xf3, 0xf4, 0xf5, 0xf6, 0xf7, 0xf8,
>>>> 0xf9, 0xfa };
>>>>
>>>> -------------------------------------------------------------------------
>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>> challenge
>>>> Build the coolest Linux based applications with Moblin SDK & win great
>>>> prizes
>>>> Grand prize is a trip for two to an Open Source event anywhere in the
>>>> world
>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>> _______________________________________________
>>>> M560x-driver-devel mailing list
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
M560x-driver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
