What should the driver output?

• To: linux-connectix@crynwr.com
• Subject: What should the driver output?
• From: Thomas Davis <Thomas.Davis@mnscorp.com>
• Date: Sun, 17 Dec 1995 23:21:26 -0600 (CST)
• From mnscorp.com!tdavis Mon Dec 18 00: 25:03 1995

Ok, I've been thinking about this one.

Let's see..

1.  The driver should be a module.
2.  The driver should have a set of IOCTL's, to set things like contrast
and brightness, scanned size (ie, 320x240, 160x120), transfer mode.

Now, my major question:

3.  _What_ should the driver output?

I've been puttering around with a driver based on someone's else driver
(that is a module, but it's really, really skeleton), and it has a
option based on how it was opened to put either bytes as is, or PGM
format (portable gray map).

4.  Status of camera?

Should it be a /proc interface?  ie, reading /proc/quickcam gives you
the current frame size, port address of camera, type of output (4bit or
6 bit), transfer type (nybble mode vs bidirectional mode), brightness
and contrast settings, or should this all be accessiable via IOCTL's ?

Personally, I like the /proc interface.  But, I'm also a believer in IOCTL's.

Decisions, decisions.

Oh, here's another one.

5. How many cameras per machine do we support?  1?  There can be 3 LPT ports,
so do we support upto 3 per machine?

-- 
Thomas Davis			| Internet:	Thomas.Davis@mnscorp.com
Systems Consultant		| Snail Mail:	Suite 528
Midwest Network Solutions Corp.	| 		1941 South 42nd Street
(402) 346-7687			|		Omaha, NE 68105-2939

• What should the driver output?
• From: nelson@crynwr.com (Russell Nelson)

• Prev: subscribe
• Next: QuickPict....
• Index: Mail Index
• Thread: Mail Thread Index