Re: SANE standard,

Robert Schwebel (r.schwebel@tu-bs.de)
Mon, 07 Dec 1998 18:43:57 +0100

becka@rz.uni-duesseldorf.de wrote:
> 2. For those that can do IO-port-only access, abstraction is as simple as
> sanei_io_[in/out][b/w/l](IO_address[,data_out]);.

Where are these functions definded? I can't find them anywhere in the
include/sane/ directory.

> 3. Installing SANE suid root is no good idea. I would thus prefer to go
> via /dev/port on Linux, which can be given appropriate permissions.

Hmmm, could you explain this in more detail? What do you mean by "via
/dev/port"?

I thought about writing a linux kernel driver for the direct hardware
dependend parts of the interface which then would be accessable vi
/dev/something and ioctl calls, but I don't either know if this was a
good idea (one more program layer) nor if this is allowed according to
platform independence. On the other hand, the hard stuff would be nicely
encapsulated. Comments?

> Well - anything that is ANSI-C should usually be o.k. . Everything else
> should only be used with care and eventually protected by autoconf.

In my case, the question is which direct io port handling routines am I
allowed to use.

Thanks a lot for your help!

Robert

-- 
 +---------------------------------------------------------------------+
 + Robert Schwebel, Fridtjof-Nansen-Strasse 51, D - 38108 Braunschweig +
 +       Public Observatory Rothwesten (near Kassel, Germany)          +
 +        phone: +49-531-353745, e-mail: r.schwebel@tu-bs.de           +
 +---------------------------------------------------------------------+

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com