Where is sane backends

Only the first 15 lines of the commit message are shown above. PR: The update to 1. Full changes between the distfiles from 1. With hat: portmgr Sponsored by: Absolight. Import upstream git commit bdc2f82dbe7e38bcc: Bugfix in kodakaio. Rely on bsdtar to autodetermine the format of the distfiles when possible For a while now bsdtar is able to autotermine compression and archive format.

Let's then use tar directly instead of piping to tar. The ports that used other USES were fixed by hand. Relative to the problem mentioned in the PR, fix the rc.

While I'm here, apply various other cleanups, including adding KEYWORD: shutdown, putting the elements in more typical order, fixing some syntax issues, etc. Bakhtin at gmail. In the rc. In cases where I had to hand-edit unusual instances also modify formatting slightly to be more uniform and in some cases, correct. Update to 1. The purpose of this backend is primarily to aid in debugging of SANE frontends.

See sane-pnm 5. See sane-pint 5. Tests frontends and the SANE installation. It provides test pictures and various test options. See sane-test 5. See sane-v4l 5. By default, all SANE backends drivers are loaded dynamically by the sane-dll meta backend. If you have any questions about the dynamic loading, read sane-dll 5. SANE frontends can also be linked to other backends directly by copying or linking a backend to libsane. It's not hard to write a SANE backend. It can take some time, however.

You should have basic knowledge of C and enough patience to work through the documentation and find out how your scanner works. Appended is a list of some documents that help to write backends and frontends.

If you start writing a backend or frontend or any other part of SANE, please contact the sane-devel mailing list for coordination so that work is not duplicated. The shared libraries implementing the backends present on systems that support dynamic loading. If your device isn't found but you know that it is supported, make sure that it is detected by your operating system.

It prints one line for each scanner it has detected and some comments. If sane-find-scanner 1 finds your scanner only as root but not as normal user, the permissions for the device files are not adjusted correctly. If the scanner isn't found at all, the operating system hasn't detected it and may need some help.

Depending on the type of your scanner, read sane-usb 5 or sane-scsi 5. If your scanner or other device is not connected over the SCSI bus or USB, read the backend's manual page for details on how to set it up.

Is your scanner detected by the operating system but not by SANE? Try scanimage -L. Some backends are commented out by default. Remove the comment sign for your backend in this case. Also some backends aren't compiled at all if one of their prerequisites are missing. If you need one of these backends and it isn't available, read the build instructions in the README file and the individual manual pages of the backends.

Another reason for not being detected by scanimage -L may be a missing or incorrect configuration in the backend's configuration file. While SANE tries to automatically find most scanners, some can't be setup correctly without the intervention of the administrator.

Also on some operating systems auto-detection may not work. Check the backend's manual page for details. If your scanner is still not found, try setting the various environment variables that are available to assist in debugging. The environment variables are documented in the relevant manual pages. The debug messages for the dll backend tell if the mustek backend was found and loaded at all. The mustek messages explain what the mustek backend is doing while the SCSI debugging shows the low level handling.

This command starts a scan for the default scanner with default settings. All the available options are listed by running scanimage --help. If scanning aborts with an error message, turn on debugging as mentioned above. Maybe the configuration file needs some tuning, e. See the backend's manual page for details. If you can't find out what's wrong, contact sane-devel.

You should get a list of PASSed tests. You can do the same with your backend by changing "test" to your backend's name. So now scanning with scanimage 1 works and you want to use one of the graphical frontends like xsane 1 , xscanimage 1 , or quiteinsane 1 but those frontends don't detect your scanner?

However, someone started working on this scanner and some information is available see link. Chinon DS One bulk-in, one bulk-out and one interrupt endpoint. Type-number: UHB21, another type nr on the inside: Compeye Simplex C. Corex Cardscan Probably unsupported at the moment. Not compatible to snapscan backend. It's not known if it may work with epson or epkowa backend. Genius ColorPage CS. Hewlett-Packard Photo Scanner Not supported by SANE. However, it's detected as mass storage device so just mounting it is reported to work.

See link for device data. Probably not supported by SANE. No details known. Maybe similar to Photo Scanner ? While an external binary-only backend exists, it works only on Linux i Therefore the scanner is unsupported on other platforms. Iris IriScan. Kodak Snapshot Photo Scanner 1. Lexmark P Probably unsupported. There seem to exist two different scanners with that name.

See link for details. Memorex u. Microtek ArtixScan Seems to be similar to the Microtek CX and is detected by the microtek2 backend. Scanning doesn't seem to work however. Probably not supported. BearPaw TA Pro. In this case it could be supported by the mustek SCSI backend.

ScanExpress USB. ScanExpress CardSmart. ScanMagic P. NEC Petiscan. Most probably unsupported. Nikon LS ED. Olivetti Job-Jet M Olympus ESP. Optrox PhotoMaker 3C. PIE Primefilm u. Primefilm Plustek OpticPro A3U. Product id 0x is unsupported but may be supported by the genesys backend in future.

Product id 0xb is supported by the gt68xx backend. Product id 0xe is supported by the gt68xx backend. Primax Colorado U. Prolink Winscan Pro U. Reflecta DigitDia Relisys Eclipse U. Scanshell N. Sicos DMS Not supported until now. Work on a backend has started, contact the author for details see link. Siemens ID Mouse Professional. Spot Technology Maxiscan A4. Syscan TravelScan FS Tamarack Artiscan Unsupported at the moment. See link for a project for that scanner that may support it in future.

Teco VMF. Tiny FUE. Trust CombiScan EasyScan UMAX Astra Vantas Visioneer Is reported to use the E5 chipset. Uses a Primax ID. Looks similar to Primascan Colorado u. Same as Microtek Scanport Same as and but includes a TA. Chipset is RTSC. Xerox Phaser MFP. Samsung X Series. Kodak DC Aiptek Aiptek Pencam.