[Prev][Next][Index][Thread]

Wow! Great progress!

Great work from Scott and Thomas!  One thing I'm wondering about is
getting a catalog of all the valid commands.  Of course the
QUICKPIC.EXE program isn't going to issue any invalid commands, so we
don't know what the sequence is for one.  But neither will it issue
any commands that it doesn't use (by definition!), so I think a little
exploration is in order, to find out which of the commands not used by
quickpic are unimplemented, and which are simply unused.

Thomas Davis writes:
 > /*
 >  * this table is based on data captured from QuickPict via Wine.
 >  */
 > 
 > int table[]={ 
 > 	0x0b, 0xbb, /* 187 Brightness       */
 > 	0x11, 0xf0, /* 240 X dimension      */
 > 	0x13, 0x50, /* 80 Y/3 (set for 320) */
 > 	0x0d, 0x01, /* 1 ?                  */
 > 	0x0f, 0x07, /* 7 ?                  */
 > 	0x19, 0x68, /* 104 - Contrast       */
 > 	0x1f, 0x64, /* 100 - WhiteBalance   */
 > 	0x07, 0x03, /* 3 Xfermode           */
 > 	0x0, 0x0

Um, I'm thinking that the 0x0d and 0x0f are commands that we don't
know about yet, and the 0x01 and 0x07 are data.  Scott's program just
outputs 0x0d, 0x01, 0x0f, and 0x07 as four bytes, but I think they're
really two commands, each with a byte of data.

 >     while ((status1 & 0x0f) != 0x08) {
 > 	status1 = inb(port+1);
 > 	count1++;
 >     }

I don't think that we need a watchdog counter on these.  We could
either just let the user control-C a hung process, or else set a timer
at the beginning of a scan, and if it fires, assume that the protocol
went south.

-russ <nelson@crynwr.com>    http://www.crynwr.com/~nelson
Crynwr Software   | Crynwr Software sells packet driver support | PGP ok
11 Grant St.      | +1 315 268 1925 voice | Good government is a contradiction
Potsdam, NY 13676 | +1 315 268 9201 FAX   | in terms.  Ask me for details.
References: