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.
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>
Not only the Perfection1650, but other scanners need to ignore the
FSG_STATUS_CANCEL_REQ bit as well. Thanks to @matc for debugging and
providing a list. Should fix#716. Remove the hardcoded bitmask while
here.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
- Stopping and releasing the device causes the ADF to purge any remaining pages,
thus only the first page gets properly scanned (observed with Samsung
SCX-4729FW).
- Instead, when sourcing from the ADF, at each page's completion it should
continue and issue "OBJECT POSITION" command to proceed to the next page.
- Once all pages have been processed, the subsequent "OBJECT POSITION" command
returns the proper "CHECK CONDITION" status (ADF is empty) and triggers the
device stop and release.
- Additionally, the status of the ADF (loaded/empty) needs to be requeried
at the `sane_start()` for proper handling of the "Auto" mode. Otherwise,
the scanning session retains the ADF state from the start of the session,
even though ADF will become empty. Thus the "Auto" mode will not properly
switch to Flatbed as intended in the client application (observed in
Simple-Scan).
> NOTE: the initial "READ" command in `sane_start()` is extraneous and
> appears to always return STATUS_BUSY (indeed, the scanner is usually
> busy loading the page). The actual READ is correctly done in
> `dev_acquire()`. It may appear benign in a single page scan mode, however,
> it becomes malfunctioning in the mutipage ADF mode. The initial READ,
> when successful, will cause the skipping of the read block from processing,
> as the actual processing is tied to content read from `dev_acquire()`.
>
> Therefore, the initial READ command in the `sane_start()` is removed.
ThierryFR