ication/octet-stream
Size: 54946 bytes
Desc: not available
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20091002/3407dd8a/attachment-0001.obj>
On Fri, October 2, 2009 11:43 am, m. allan noah wrote:
> On Fri, Oct 2, 2009 at 11:53 AM, wrote:
>> I'm back at considering working on a driver for the Canoscan 8400f. I
>> have
>> been requested by another developer to help do this. I have the Mac
>> driver. Mac, if I remember it is *nix based n
On Fri, Oct 2, 2009 at 11:53 AM, wrote:
> I'm back at considering working on a driver for the Canoscan 8400f. I have
> been requested by another developer to help do this. I have the Mac
> driver. Mac, if I remember it is *nix based now. What is the take on
> driver writing in regards to RE drive
I'm back at considering working on a driver for the Canoscan 8400f. I have
been requested by another developer to help do this. I have the Mac
driver. Mac, if I remember it is *nix based now. What is the take on
driver writing in regards to RE drivers to implement drivers? Has anyone
ever decompile
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20091002/2c9f382d/attachment.pgp>
two options:
1. make it look like any other powered-off scanner, and dont expose
the it to the user. scanimage -L wont show it, and the user will
think- oh, need to push the power button. (it will still show in
sane-find-scanner, however, most users dont run that)
2. see if the windows driver has
Le vendredi 2 octobre 2009 04:30:09 Paul Wise, vous avez ?crit :
> Hi all,
>
> [Please CC me, I'm not subscribed]
>
> The scanner I'm working on (Lexmark X2330) shows up in USB when the
> scanner has wall power but the blue LED embedded in the power on button
> is off. When in that state, the scann
Hello,
I found a bug that explains the dark scans obtained. Even though the
scanner
didn't have shading calibration, scans were done with hardware shading
correction enabled. Since no calibration data was sent before scan, we got
black scans.
I have committed a fix for
