[sane-devel] LIDE210 5th button. sane-devel Digest, Vol 91, Issue 33
Michael Watson
mwatson33 at comcast.net
Sat Jan 26 03:31:48 UTC 2013
All,
The existing lide 210 code supports 4/5 buttons. I have 5/5 working
temporarily (call it a hack) utilizing the enum OPT_PAGE_LOADED_SW that this
scanner does not have.
genesys_gl124.c (search for button)
For the lide210 case add
if (s->val[OPT_PAGE_LOADED_SW].b ==
s->last_val[OPT_PAGE_LOADED_SW].b)
s->val[OPT_PAGE_LOADED_SW].b = (val & 0x01) == 0;
genesys_devices.c
Add "| GENESYS_HAS_PAGE_LOADED_SW" to static Genesys_Model
canon_lide_210_model
scanbd.conf
add an action with filter = "^page.*"
I do not understand the code that well to make a real 5th button addition.
In genesys_low.h the options are defined (e.g. #define
GENESYS_HAS_PAGE_LOADED_SW (1 << 4)) and all the bits could be used up with
all the definitions. If it's portable we may have only 8 and they are used
up.
R/
Michael
-----Original Message-----
From: sane-devel-bounces+mwatson33=comcast.net at lists.alioth.debian.org
[mailto:sane-devel-bounces+mwatson33=comcast.net at lists.alioth.debian.org] On
Behalf Of sane-devel-request at lists.alioth.debian.org
Sent: Friday, January 25, 2013 7:00 AM
To: sane-devel at lists.alioth.debian.org
Subject: sane-devel Digest, Vol 91, Issue 33
Send sane-devel mailing list submissions to
sane-devel at lists.alioth.debian.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
or, via email, send a message with subject or body 'help' to
sane-devel-request at lists.alioth.debian.org
You can reach the person managing the list at
sane-devel-owner at lists.alioth.debian.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of sane-devel digest..."
Today's Topics:
1. Re: Scanner Button Daemon [scanbd]: conf and script files for
Canoscan 9000F (Nelson)
2. Re: backend distribution question (Johannes Meixner)
3. Re: backend distribution question (Ruell Magpayo)
----------------------------------------------------------------------
Message: 1
Date: Fri, 25 Jan 2013 08:43:23 +0100
From: Nelson <haha at mehr4u.de>
To: Rolf Bensch <rolf at bensch-online.de>
Cc: Mailingliste Sane <sane-devel at lists.alioth.debian.org>
Subject: Re: [sane-devel] Scanner Button Daemon [scanbd]: conf and
script files for Canoscan 9000F
Message-ID: <796EE27D-F7B8-4ECF-B061-AFADE988F26B at mehr4u.de>
Content-Type: text/plain; charset=us-ascii
> Hi list,
>
> After fixing button support for my CS9000F (already committed to git),
> I installed scanbd on my Ubuntu 12.04 system. During some testing I
> created a scanbd conf file and two script files, which I want to share
> with the ml.
>
> Save 'cs9000f.conf' and 'cs9000f.sh' to
> '/usr/local/etc/scanbd/scanner.d/' and scanb to '/usr/local/bin/'.
> Then 'sudo chmod 755 [path]scanb' and 'sudo chmod 755
> [path]cs9000f.sh'. Last but not least you must append this line to
> '/usr/local/etc/scanbd/scanbd.conf':
> 'include(scanner.d/cs9000f.conf)'.
>
> It is recommended that you setup scanbd before you can use any
> scanner. There are several manuals in the internet, e.g.
> http://thehomeserverhandbook.com/2012/03/03/scanbd_part1/ or
> http://www.mehr4u.de/component/k2/item/99-mit-scanbd-scannertasen-an-e
> inem-canon-mx700-nutzen.html
> ...
>
> Some background infos:
>
> The CS9000F has 7 push buttons: Auto Scan, PDF Color, PDF Gray, PDF
> User, PDF End, Copy and E-Mail.
>
> scanbd is reading all buttons as '--target' [1..7] from sane, button
> 'PDF End' (target 5) as '--button-2' and all other buttons (targets
> 1-4 and 6-7) as '--button-1' from sane. You can check the scanner
> buttons behaviour with 'scanimage -A'.
>
> 'cs9000f.conf' is the configuration file of scanbd and converts sane
> targets to scanbd actions.
>
> 'cs9000f.sh' is the shell script which is called at every push button.
> The button equivalent scanbd actions are: auto-scan, pdf-color,
> pdf-gray, pdf-user, pdf-end, copy and email.
>
> Please adapt $SCANDIR and $PRINTER in 'cs9000f.sh' to your system's
> needs.
>
> 'scanb' is a wrapper script for the scanbd daemon, so that scanbd
> isn't blocking my scanner. I can use 'xsane' for scanning from a gui
> with preview and 'scanbd' for button controlled stupid scanning
> multiple pages. 'scanb' can be called with scanimage's scan options
> which are passed on the auto-scan action.
>
> Please feel free to send me any feedback.
>
> Cheers,
> Rolf
>
> <cs9000f.conf>
> <cs9000f.sh>
> <scanb>
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
> to sane-devel-request at lists.alioth.debian.org
Hey,
please use the next time the corrected link.
http://www.mehr4u.de/component/k2/item/99-mit-scanbd-scannertasten-an-einem-
canon-mx700-nutzen.html
Best Regards
Nelson
------------------------------
Message: 2
Date: Fri, 25 Jan 2013 11:17:41 +0100 (CET)
From: Johannes Meixner <jsmeix at suse.de>
To: sane-devel at lists.alioth.debian.org
Subject: Re: [sane-devel] backend distribution question
Message-ID: <alpine.LNX.2.00.1301250956550.3375 at nelson.suse.de>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Hello,
On Jan 25 02:39 Ruell Magpayo wrote (excerpt):
> I would like to define by what I mean by: "Kyocera home based MFP
> devices" It refers to the newly released(2012) low-cost printers from
> Kyocera; FS-1020, FS-1125, FS-1120 series
>
> Some of these products have network interface but because
> it is low-cost MFP, it does not have the scan to email feature unlike
> the other Kyocera products.
>
> All processing from these devices are done at host PC side including
> the image processing. We are considering options on how to support
> linux scan...
To support scanning under Linux the only reasonable way is
to provide a driver/backend for SANE because scanning via SANE is
practically the only way how scanning happens under Linux.
The only reasonable way to provide a SANE backend to Linux users is to make
the backend in a way so that Linux distributors can include it in the Linux
distributions and that means to make the backend as free software.
Now you (i.e. Kyocera) has the issue that you need to use
confidential/proprietary functionality which cannot be implemented as free
software.
I.e. you have the issue that you need run proprietary software.
As I explained in my previous mail, separation of proprietary software from
free software is essential.
Therefore you (i.e. Kyocera) must keep your proprietary stuff only on your
servers but you would openly release your free software so that others can
integrate your free software (and only your free software) into SANE and
this way also into Linux distributions.
When your SANE backend runs on the end-user's computer
and when it needs the proprietary functionality,
it has to execute your proprietary stuff preferably
as separated process as I explained in my previous mail.
This means your proprietary stuff must exist as executable
on the end-user's computer.
Therefore Kyocera has to provide its proprietary stuff on Kyocera servers
for download and installation by end-users.
End-user machines are usually x86/i386/i486/i586 (32-bit)
or x86_64 (64-bit) so that Kyocera has to provide its proprietary stuff at
least for those two architectures.
Accordingly Kyocera also has to provide a download and installation tool so
that end-users can easily download and install the right proprietary stuff
from the right Kyocera servers on the end-user's computer (showing the right
license dialogs and all what is needed to do this part correctly).
The Kyocera installation tool must also be free software
so that Kyocera users get it "out of the box" in the
Linux distributions.
At least we (i.e. SUSE/openSUSE) can only provide a
free software Kyocera installation tool "as is" and
we could even run such a tool "as is" if needed
(currently our YaST printer setup module can launch
HP's hp-setup tool "as is" to set up HP devices).
But we would never ever download and install proprietary
stuff from Kyocera on our own (e.g. implement such
a tool on our own) because we will never ever risk
any kind of legal issue because of proprietary stuff
that is required by weak (low-cost) hardware, see
http://en.opensuse.org/SDB:GDI_Printers
Perhaps the Kyocera installation tool cannot be integrated
in SANE. Whether or not this is possible depends on what
the SANE developers decide here.
If the Kyocera installation tool cannot be integrated in SANE, Kyocera must
provide it as separated free source code package so that Linux distributors
can build it separated from SANE.
If your proprietary executable does not exist on the
end-user's computer, your SANE backend must exit appropriately preferably
with a meaningful error message that informs the user that your proprietary
stuff needs to be downloaded from Kyocera.
This way how to deal with the issue when confidential/proprietary
functionality is needed by free software is currently used by HPLIP (see
http://hplipopensource.com/hplip-web/index.html)
when HP printers or all-in-one devices require proprietary functionality,
see https://bugzilla.novell.com/show_bug.cgi?id=342704
in particular https://bugzilla.novell.com/show_bug.cgi?id=342704#c3
This way works optimal for end-users, Linux distributors,
and free software developers ("optimal" means at least currently there is no
better way known how to deal with the issue).
This way is more software programming effort for the manufacturer (keeping
separated parts actually strictly separated instead of mixing up everything
into one big software monster mess).
But on the other hand this way avoids any other trouble
in particular legal issues because of the licensing.
In particular for software developers at the manufacturer
it means that they can "just do their job" (i.e. "just making their
software") which they probably like a bit more than to deal with their legal
department and the legal department of the Free Software Foundation and the
legal departments of various Linux distributors ;-)
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
------------------------------
Message: 3
Date: Fri, 25 Jan 2013 10:30:54 +0000
From: Ruell Magpayo <Ruell.Magpayo at ddp.kyocera.com>
To: Johannes Meixner <jsmeix at suse.de>,
"sane-devel at lists.alioth.debian.org"
<sane-devel at lists.alioth.debian.org>
Subject: Re: [sane-devel] backend distribution question
Message-ID:
<722AF2BB389DED4C84FCCCC74963FCB756916EEE at KTDPSVREX.ktdp.local>
Content-Type: text/plain; charset="us-ascii"
Got it, thanks for your support!
-----Original Message-----
From:
sane-devel-bounces+ruell.magpayo=ddp.kyocera.com at lists.alioth.debian.org
[mailto:sane-devel-bounces+ruell.magpayo=ddp.kyocera.com at lists.alioth.debian
.org] On Behalf Of Johannes Meixner
Sent: Friday, January 25, 2013 6:18 PM
To: sane-devel at lists.alioth.debian.org
Subject: Re: [sane-devel] backend distribution question
Hello,
On Jan 25 02:39 Ruell Magpayo wrote (excerpt):
> I would like to define by what I mean by: "Kyocera home based MFP
> devices" It refers to the newly released(2012) low-cost printers from
> Kyocera; FS-1020, FS-1125, FS-1120 series
>
> Some of these products have network interface but because it is
> low-cost MFP, it does not have the scan to email feature unlike the
> other Kyocera products.
>
> All processing from these devices are done at host PC side including
> the image processing.
> We are considering options on how to support linux scan...
To support scanning under Linux the only reasonable way is to provide a
driver/backend for SANE because scanning via SANE is practically the only
way how scanning happens under Linux.
The only reasonable way to provide a SANE backend to Linux users is to make
the backend in a way so that Linux distributors can include it in the Linux
distributions and that means to make the backend as free software.
Now you (i.e. Kyocera) has the issue that you need to use
confidential/proprietary functionality which cannot be implemented as free
software.
I.e. you have the issue that you need run proprietary software.
As I explained in my previous mail, separation of proprietary software from
free software is essential.
Therefore you (i.e. Kyocera) must keep your proprietary stuff only on your
servers but you would openly release your free software so that others can
integrate your free software (and only your free software) into SANE and
this way also into Linux distributions.
When your SANE backend runs on the end-user's computer and when it needs the
proprietary functionality, it has to execute your proprietary stuff
preferably as separated process as I explained in my previous mail.
This means your proprietary stuff must exist as executable on the end-user's
computer.
Therefore Kyocera has to provide its proprietary stuff on Kyocera servers
for download and installation by end-users.
End-user machines are usually x86/i386/i486/i586 (32-bit) or x86_64 (64-bit)
so that Kyocera has to provide its proprietary stuff at least for those two
architectures.
Accordingly Kyocera also has to provide a download and installation tool so
that end-users can easily download and install the right proprietary stuff
from the right Kyocera servers on the end-user's computer (showing the right
license dialogs and all what is needed to do this part correctly).
The Kyocera installation tool must also be free software so that Kyocera
users get it "out of the box" in the Linux distributions.
At least we (i.e. SUSE/openSUSE) can only provide a free software Kyocera
installation tool "as is" and we could even run such a tool "as is" if
needed (currently our YaST printer setup module can launch
HP's hp-setup tool "as is" to set up HP devices).
But we would never ever download and install proprietary stuff from Kyocera
on our own (e.g. implement such a tool on our own) because we will never
ever risk any kind of legal issue because of proprietary stuff that is
required by weak (low-cost) hardware, see
http://en.opensuse.org/SDB:GDI_Printers
Perhaps the Kyocera installation tool cannot be integrated in SANE. Whether
or not this is possible depends on what the SANE developers decide here.
If the Kyocera installation tool cannot be integrated in SANE, Kyocera must
provide it as separated free source code package so that Linux distributors
can build it separated from SANE.
If your proprietary executable does not exist on the end-user's computer,
your SANE backend must exit appropriately preferably with a meaningful error
message that informs the user that your proprietary stuff needs to be
downloaded from Kyocera.
This way how to deal with the issue when confidential/proprietary
functionality is needed by free software is currently used by HPLIP (see
http://hplipopensource.com/hplip-web/index.html)
when HP printers or all-in-one devices require proprietary functionality,
see https://bugzilla.novell.com/show_bug.cgi?id=342704
in particular https://bugzilla.novell.com/show_bug.cgi?id=342704#c3
This way works optimal for end-users, Linux distributors, and free software
developers ("optimal" means at least currently there is no better way known
how to deal with the issue).
This way is more software programming effort for the manufacturer (keeping
separated parts actually strictly separated instead of mixing up everything
into one big software monster mess).
But on the other hand this way avoids any other trouble in particular legal
issues because of the licensing.
In particular for software developers at the manufacturer it means that they
can "just do their job" (i.e. "just making their software") which they
probably like a bit more than to deal with their legal department and the
legal department of the Free Software Foundation and the legal departments
of various Linux distributors ;-)
Kind Regards
Johannes Meixner
--
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
--
sane-devel mailing list: sane-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-request at lists.alioth.debian.org
------------------------------
_______________________________________________
sane-devel mailing list
sane-devel at lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
End of sane-devel Digest, Vol 91, Issue 33
******************************************
More information about the sane-devel
mailing list