- re-ordered the new option into the block of enums for the panel
- re-ordered the code to reflect the new value of OPT_FUNCTION_NUMBER
- corrected size of variable panel_read to include the new option OPT_FUNCTION_NUMBER
This change adds support for the function number configuration on the
Canon DR-3010C panel display. The function number can be used to
start different actions by "scanbd" when the start button is hit.
Support in scanbd must be configured appropriately.
The new SANE sensor has the name "function-number".
1.3.0 got out into the wild even though it didn't really work properly.
A few distros have expressed a desire for a 1.3.1 to replace it due
to reproducability reasons.
We can use the output of this to manually create the release if it
fails automatically. We needs the generated paths to provide to the
manual operation in the GitLab GUI.
My intended use case is the following:
I want to compile saned backends with different libraries (for example
glibc) than a specific application (as if it were a chroot of another
distro version). This application cannot dlopen sane
backends because of the library mismatch.
The specific application will be
built with a stripped down libsane that only has the net backend,
and therefore very few dependencies. The net backend points to saned.
saned has a full config and set of backends, and is responsible for
exporting all scanners to the application. This option allows to
reexport network scanners this way. I only have to make sure saned does
not contact itself.
Make it easier for users to find the proper firmware by documenting it
in the comments section. I wrote a script to extract the data from the
driver and then manually verified/corrected it.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Make it easier for users to find the proper firmware by documenting it
in the comments section. I wrote a script to extract the data from the
driver and then manually verified/corrected it.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Make it easier for users to find the proper firmware by documenting it
in the comments section. I wrote a script to extract the data from the
driver and then manually verified/corrected it. Some model names needed
updates to match their entry in the sourcecode.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
ThierryFR