Erik, Accord

There were also some questions formulated by Frank Bourdonnec. See the 
mailing list.

> Q1
> The .csr text file lists of lot of register directly mapped to variables
> into m5603 code loaded from the .bin file (microcode is a classic 8052)
> during startup of the chip
>
> Can they provide more data about that?
>
> Q2
> Describe the start of frame mechanism
> for the ali5603c
>   


Can you please include those.

Willem

Erik Andrén wrote:
> Hi,
>
> There now are some questions on the wiki page listed below.
> How shall we proceed?
> Shall we try to break all questions into subset questions and feem 
> them one-by-one to lower the threshold of answering?
> If so, what would be a good introduction question?
>
> An example of simple question that I would like to have answered is:
> What does the M5602_XB_SENSOR_TYPE register in the m5602 do, and what 
> does the different bits represent?
>
> Regards,
> Erik
>
> 2008/6/10 Erik Andrén <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>>:
>
>     Hi,
>
>     2008/6/10 Accord Tsai <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>>:
>
>         Yes, I second the opinion to ask specific questions. Now that
>         we have
>         direct contact with personnel inside ALi, we should gather the
>         information we need. By asking direct questions we can
>         circumvent the
>         company policy troubles.
>
>         Perhaps we should compile a list of questions to forward to ALi?
>
>
>     Good idea!
>
>     I've created a page stub in the m560x wiki at
>     http://m560x-driver.wiki.sourceforge.net/ALi_Questions
>
>     Please add your questions there in a logical way.
>
>     Thanks,
>     Erik
>      
>
>
>
>         Accord
>
>         On Tue, Jun 10, 2008 at 5:53 PM,  <[EMAIL PROTECTED]
>         <mailto:[EMAIL PROTECTED]>> wrote:
>         > Hello
>         >
>         > Although I have not been active lately, I am still reading
>         the mailing
>         > list. My opinion is we should ask Ali specific questions on
>         details we
>         > have not been able to figure out yet. One is the long
>         standing issue of
>         > the hardware jpeg-encoding within the m5603. I would like to
>         know what the
>         > huffman-tables and the quantization tables are. They are in
>         the hardware
>         > and without then takes a lot of trial and error to recover a
>         simple
>         > picture, basically not being able to use functionality.
>         >
>         > There are probably also other issues like the white-balancing,
>         > contrast-enhancement.
>         >
>         > I also have a mt9v111 camera working (Creative Live cam
>         voice). I have the
>         > old usb-snoops from andrea somewhere. I will send them when
>         I find them. I
>         > will also try to post the necessary initialization. Although
>         you can find
>         > it also in the testprograms, which where used to get
>         andrea's first still
>         > pictures (about two years ago?)
>         >
>         > Willem
>         >
>
>         
> -------------------------------------------------------------------------
>         Check out the new SourceForge.net Marketplace.
>         It's the best place to buy or sell services for
>         just about anything Open Source.
>         http://sourceforge.net/services/buy/index.php
>         _______________________________________________
>         M560x-driver-devel mailing list
>         [email protected]
>         <mailto:[email protected]>
>         https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel
>
>
>


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
M560x-driver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m560x-driver-devel

Reply via email to