[sane-devel] [FYI] new ls5000 backend
Johannes, Comments in your code suggest you have documentation on the LS-5000. If so, does it say how to use the calibration data? John Date: Fri, 11 May 2007 14:58:26 +0200 From: Johannes Berg johannes at sipsolutions.net Subject: [sane-devel] [FYI] new ls5000 backend To: Major A andras at users.sourceforge.net Cc: Ariel Garcia garcia at iwr.fzk.de, Spiro Angeli Spiro at siriush.com, sane-devel at lists.alioth.debian.org Message-ID: 117306.8896.22.camel at johannes.berg Content-Type: text/plain; charset=us-ascii Hi, Because coolscan2 doesn't work with my Coolscan 5000 ED film scanner I more or less rewrote coolscan2 as ls5000. During the cleanup I removed support for all other scanners, it shouldn't be too hard to add back in. Things I changed: * use C99 constructs for easier command packing * clean up coding style to conform to something I can work with * remove LS-40/4000/... support * add LS-5000 support (the coolscan2 package claims to support it but it doesn't work) * add grayscale support * clean up options * rip out the sane_read implementation and replace with something sane (excuse the pun) * add lots of comments about what the backend is doing * possibly lots more I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. The project has a tiny website at http://johannes.sipsolutions.net/Projects/ls5000, code is available via git clone http://git.sipsolutions.net/ls5000.git (and that URL also works as a gitweb URL) johannes
[sane-devel] [FYI] new ls5000 backend
Johannes Berg johan...@sipsolutions.net wrote: Hi, I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. I've added ls5000 to sane-backends-extras 1.0.18.8. JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] [FYI] new ls5000 backend
Johannes Berg johan...@sipsolutions.net wrote: Hi, I've added ls5000 to sane-backends-extras 1.0.18.8. Oh, I'll probably have to submit a patch than that prevents coolscan2 from binding the ls5000. Yep, that'll be needed. Though LS-5000 owners won't use coolscan2 so they can just disable it and be done with it. Note that we really need something more general to fix that, because we have the same problem with epson and epson2 stepping on each other's toes in the CVS (and then there's epkowa ... 3 backends for epson scanners, and I'm not counting the snapscan backend ...). JB. -- Julien BLACHE http://www.jblache.org j...@jblache.org GPG KeyID 0xF5D65169
[sane-devel] [FYI] new ls5000 backend
Hi, I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. I've added ls5000 to sane-backends-extras 1.0.18.8. Oh, I'll probably have to submit a patch than that prevents coolscan2 from binding the ls5000. johannes -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 190 bytes Desc: This is a digitally signed message part Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070512/c9047a2b/attachment.pgp From johan...@sipsolutions.net Sat May 12 09:29:22 2007 From: johan...@sipsolutions.net (Johannes Berg) Date: Sat May 12 10:55:09 2007 Subject: [sane-devel] [FYI] new ls5000 backend In-Reply-To: 1178961968.2647.7.ca...@johannes.berg References: 117306.8896.22.ca...@johannes.berg 871whme7lf@sonic.technologeek.org 1178961968.2647.7.ca...@johannes.berg Message-ID: 1178962162.2647.10.ca...@johannes.berg On Sat, 2007-05-12 at 11:26 +0200, Johannes Berg wrote: Oh, I'll probably have to submit a patch than that prevents coolscan2 from binding the ls5000. This should work. It doesn't prevent it from claiming the USB interface but then queries the scanner and if it's a LS-5000 gives up, that *should* give ls5000 a chance to be queried as the next scanner if I correctly understand how querying works. johannes --- sane-backends-1.0.18.orig/backend/coolscan2.c 2007-05-12 11:26:31.0 +0200 +++ sane-backends-1.0.18/backend/coolscan2.c2007-05-12 11:28:00.0 +0200 @@ -1791,8 +1791,6 @@ cs2_open (const char *device, cs2_interf s-type = CS2_TYPE_LS2000; else if (!strncmp (s-product_string, LS-4000 ED , 16)) s-type = CS2_TYPE_LS4000; - else if (!strncmp (s-product_string, LS-5000 ED , 16)) -s-type = CS2_TYPE_LS5000; else if (!strncmp (s-product_string, LS-8000 ED , 16)) s-type = CS2_TYPE_LS8000;
[sane-devel] [FYI] new ls5000 backend
If anybody wants to do it, all the better, but if it makes the code as unreadable and stupid as it was in coolscan2.c (like parsing bytes from a string at runtime...) then I will not take such a patch nor help maintain a forked version. Please note that the author of coolscan2 is reading this list and might be offended by such unqualified and inappropriate remarks. Or is my code really that bad? Or maybe the stupid functions you refer to were added by others? Trying to use the latest language features is one thing, writing robust and portable code is another. If you can't read the latter, there isn't much I can do. Andras
[sane-devel] [FYI] new ls5000 backend
Hi, Because coolscan2 doesn't work with my Coolscan 5000 ED film scanner I more or less rewrote coolscan2 as ls5000. During the cleanup I removed support for all other scanners, it shouldn't be too hard to add back in. Things I changed: * use C99 constructs for easier command packing * clean up coding style to conform to something I can work with * remove LS-40/4000/... support * add LS-5000 support (the coolscan2 package claims to support it but it doesn't work) * add grayscale support * clean up options * rip out the sane_read implementation and replace with something sane (excuse the pun) * add lots of comments about what the backend is doing * possibly lots more I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. The project has a tiny website at http://johannes.sipsolutions.net/Projects/ls5000, code is available via git clone http://git.sipsolutions.net/ls5000.git (and that URL also works as a gitweb URL) johannes -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 190 bytes Desc: This is a digitally signed message part Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070511/71b4025c/attachment.pgp From r...@exactcode.de Fri May 11 14:03:14 2007 From: r...@exactcode.de (=?iso-8859-1?q?Ren=E9_Rebe?=) Date: Fri May 11 14:04:18 2007 Subject: [sane-devel] [FYI] new ls5000 backend In-Reply-To: 117306.8896.22.ca...@johannes.berg References: 117306.8896.22.ca...@johannes.berg Message-ID: 200705111603.15150.r...@exactcode.de Hi Johannes :-) On Friday 11 May 2007 14:58:26 you wrote: Because coolscan2 doesn't work with my Coolscan 5000 ED film scanner I more or less rewrote coolscan2 as ls5000. During the cleanup I removed support for all other scanners, it shouldn't be too hard to add back in. Things I changed: * use C99 constructs for easier command packing ... I don't plan to submit any patches to coolscan2.c because that code is in my eyes horrible to work with. I also don't plan to submit ls5000.c to SANE because apparently SANE still requires that the backend builds with ancient compilers. Indeed SANE is suppost to build on various other, aging Un*x flavours and this is why so far no backend does use C99 features (at least as far as I know and I also avoided it in my Avision backend as well). Yours, -- Ren? Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
[sane-devel] [FYI] new ls5000 backend
Hi Ren?, Indeed SANE is suppost to build on various other, aging Un*x flavours and this is why so far no backend does use C99 features (at least as far as I know and I also avoided it in my Avision backend as well). Yeah, I know, that's why I said I don't plan to submit it. I have better things to do than try making this compile on ancient^Waging systems :) If anybody wants to do it, all the better, but if it makes the code as unreadable and stupid as it was in coolscan2.c (like parsing bytes from a string at runtime...) then I will not take such a patch nor help maintain a forked version. johannes -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 190 bytes Desc: This is a digitally signed message part Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070511/6ff272d3/attachment.pgp From kevin.molo...@colorado.edu Fri May 11 15:10:21 2007 From: kevin.molo...@colorado.edu (Kevin Moloney) Date: Fri May 11 15:10:31 2007 Subject: [sane-devel] Crash problem with Nikon LS-20 on Ubuntu 7.04 PPC Message-ID: ad21130c-44cb-4a8d-a301-0c0997181...@colorado.edu Hello Sane people, I'm trying to revive my old Nikon LS-20 SCSI scanner on an Apple Powerbook G3 Wallstreet running Ubuntu 7.04. The SANE distro included with Ubuntu initially recognizes the scanner, but then pops up an error message two or three times saying: Failed to obtain value of option source: Invalid argument. After closing the error message for the third time, SANE crashes. Then I can't access the scanner without a reboot. Suggestions? Permissions problem? SCSI problem? Hardware problem? SANE has worked before with this scanner, on the same machine but running YDL 4. I'm not the most fluent in Linux, so if the answer is obvious, my apologies. Kevin -- When people start talking of man's inhumanity to man it means they actually haven't walked far enough. -- Bruce Chatwin Kevin Moloney Photography 303/604-9860 phone http://www.KevinMoloney.com/
