Hi,
On Thu, Nov 23, 2000 at 03:38:06PM -0800, David Paschal wrote:
> Currently, PTAL and its associated low-level kernel drivers support
> peripherals attached to the parallel port of the computer, or to a LAN
> using an HP JetDirect external print server. In the future I plan to add
> USB support as well. All of this is transparent to SANE, however. So
> just saying "Parport" would be a little inaccurate. For now I could say
> "Parport(ECP) and JetDirect 70X/170X/300X/500X", and later when I add USB
> support to PTAL I could come back and update hp.desc, but that's getting
> rather long. What would you suggest to do about this?
I don't know JetDirect. Is the scanner connected to the JetDirect
server by a parport cable and the server by ethernet to the computer?
In this case use Parport (ECP) and add something like "JetDirect
servers also supported" to :comment.
If there is a network port on the scanner itsself
:interface "Parport (ECP), Ethernet" (or JetDirect instead of
Ethernet) would be ok.
The sane-backends pages doesn't need to have all details about the
scanner, it's just an overview. You can put more information on the
backend's homepage, e.g. which JetDirect servers exactly are supported
and to which degree the scanners work.
> Got it. Is this OK?:
> :model "HP OfficeJet K series"
> :comment "partial support -- requires extra steps to scan successfully"
That's ok.
> :interface "PTAL"
See above.
Bye,
Henning
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Fri Nov 24 2000 - 12:36:12 PST