[sane-devel] Listen =?
merc1984 at f-m.fm writes: I need to set saned to listen only on 127.0.0.1. But I've searched far and wide and have not found any way to make it do this. The Listen = 127.0.0.1 imperative in saned.conf doesn't work. Any way to do this? Just make localhost the only entry in your /etc/sane.d/saned.conf. BTW, a Listen directive is normally used to restrict the *ports* on which a daemon listens, not the hosts that are allowed to connect. To restrict the ports, use the data_portrange option. For details on the configuration see the saned manual page. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[sane-devel] Xsane Scanner Software
I was running this software without any problems. However when I now open the programme all of the various dialogue boxes seem to open but then all but one disappear. How can I ensure that they remain open. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121012/2be95030/attachment.html
[sane-devel] Listen =?
merc1984 at f-m.fm writes: On Thu, Oct 11, 2012, at 16:33, Olaf Meeuwissen wrote: Just make localhost the only entry in your /etc/sane.d/saned.conf. BTW, a Listen directive is normally used to restrict the *ports* on which a daemon listens, not the hosts that are allowed to connect. To restrict the ports, use the data_portrange option. For details on the configuration see the saned manual page. Everyone misunderstands my question. I am not wanting to limit -access- to only localhost. Sorry for misreading your question. I want the daemon (in network mode) to only -bind- to 127.0.0.1 . Not any other IP. And listen or bind are variously the correct directives, depending on the daemon. There's no documented way of doing this. You could check the code but I don't think this is supported. Feel free to contribute a patch ;-) Hope this helps, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
[sane-devel] Problem with developing a new backend for Plustek OpticPro ST28
On 11/10/2012 19:51, Yury Tarasievich wrote: I'm willing to cross-test what you'll be producing for the ST28, as I have one also, but have currently no time to put into development. On 10/11/2012 06:38 PM, Mohammad-Reza Nabipoor wrote: ... And, according to my scanner board: * It is a GL841-based scanner * It uses ILX569K CCD. (same as of ST24 (according to the genesys_low.h)). * It uses L6219 stepper motor driver. * It uses Wolfson WM8196 Frontend. If I understand correctly what Stef tells us, this kind of information, surprisingly, is almost of no use when developing the new frontend, as mostly this consists of parsing the windows usb traces. Yury Hello, these hardware information can help us to find how close to another scanner a specific model is. Since the ST24 is an unsupported GL646 scanner, it is not as helpful as it could have been. Even when hardware is known, you'll have to know exactly how they are wired to adapt the backend without to have to look at the windwos usb snoop logs. One common source of differences are the GPIO, which are enough to prevent an unsupported scanner to work until they are correctly set. For all the steps you may have to take to add support, look at the various exchanges in the mailing list on adding support for the plustek Opticbook 3600 between me and Chris Berry . This scanner is the same kind of target than yours. Regards, Stef -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121012/2de1aeba/attachment.html
[sane-devel] Problem with developing a new backend for Plustek OpticPro ST28
On 10/12/2012 07:57 AM, Stef wrote: these hardware information can help us to find how close to another scanner a specific model is. Since the ST24 is an unsupported GL646 scanner, it is not as helpful as it could have been. Even when hardware is known, you'll have to know exactly how they are wired to adapt the backend without to have to look at the windwos usb snoop logs. ... add support, look at the various exchanges in the mailing list on adding support for the plustek Opticbook 3600 between me and Chris Berry . This scanner is the same kind of target Thank you, of course. And please, guys, include me in CC for the eventually produced sources for ST28. Mohammad-Reza, for ST28 (being added) to be recognized, you'll need to add the USB IDs both to genesys_devices.c (genesys_usb_device_list structure) and to genesys.conf.in. One mighty source of confusion for Genesys backends writers is, I believe, the frontend concept and the corresponding Genesys_Frontend structure. (It is for me :) I gave it a brief re-look right now. I still don't understand this part of the genesys source code. How exactly one is supposed to program something like ILX569 sensor, which is only controlled by the appropriate clocking signal (from GL841, to be sure). Or WM8196 DAC coupled to it, which is, too, clocked only? (I'm looking at their datasheets) Yury
[sane-devel] Problem with developing a new backend for Plustek OpticPro ST28
Dear Yury The 'Frontend' in Genesys_Frontend refers to Analogue Front End (AFE) IC. Genesys_Frontend structure contains some data (e.g. offset) for the WM8196 (that, is a 16-bit analogue front end/digitiser IC which processes and digitises the analogue output signals from CCD sensors or Contact Image Sensors (CIS)). As mentioned in WM8196 datasheet, it has Programmable gain and Programmable offset adjust, so we can set these parameters in the Genesys_Frontend structure. (And, there are two other entries in the Genesys_Frontend that I don't understand them, yet! -- can anyone help me?). Yury, as I mentioned in my first email, I am not sure that my scanner is a ST28(!); can you help me to understand it? please check your scanner VID/PID and compare them with 0x07b3/0x0802. Regards, Mohammad-Reza - Original Message - From: Yury Tarasievich yury.tarasiev...@gmail.com To: sane-devel at lists.alioth.debian.org sane-devel at lists.alioth.debian.org Cc: Sent: Friday, 12 October 2012, 9:34 Subject: Re: [sane-devel] Problem with developing a new backend for Plustek OpticPro ST28 On 10/12/2012 07:57 AM, Stef wrote: ? ? ? these hardware information can help us to find how close to another scanner a specific model is. Since the ST24 is an unsupported GL646 scanner, it is not as helpful as it could have been. Even when hardware is known, you'll have to know exactly how they are wired to adapt the backend without to have to look at the windwos usb snoop logs. ... add support, look at the various exchanges in the mailing list on adding support for the plustek Opticbook 3600 between me and Chris Berry . This scanner is the same kind of target Thank you, of course. And please, guys, include me in CC for the eventually produced sources for ST28. Mohammad-Reza, for ST28 (being added) to be recognized, you'll need to add the USB IDs both to genesys_devices.c (genesys_usb_device_list structure) and to genesys.conf.in. One mighty source of confusion for Genesys backends writers is, I believe, the frontend concept and the corresponding Genesys_Frontend structure. (It is for me :) I gave it a brief re-look right now. I still don't understand this part of the genesys source code. How exactly one is supposed to program something like ILX569 sensor, which is only controlled by the appropriate clocking signal (from GL841, to be sure). Or WM8196 DAC coupled to it, which is, too, clocked only? (I'm looking at their datasheets) Yury -- 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 -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121012/d35f9924/attachment.html
[sane-devel] Problem with developing a new backend for Plustek OpticPro ST28
You are right, there are couple of registers in Wolfson DACs, accessed via some sort of specific serial interface. The frontend -- as the Genesys GL* datasheets understand the word. Never mind. My scanner is indeed ST28 with USB IDs 0x7B3 0x802. So yours would be, too. Your hardware list fits perfectly what I saw in mine and what I was told by manufacturer. Yury
[sane-devel] Listen =?
merc1984 at f-m.fm writes: I want the daemon (in network mode) to only -bind- to 127.0.0.1 . Not any other IP. And listen or bind are variously the correct directives, depending on the daemon. To which I replied: There's no documented way of doing this. You could check the code but I don't think this is supported. Feel free to contribute a patch ;-) Which made merc1984 at f-m.fm say: Astounding. First time I've seen this. I'm a real estate developer, not a coder, so can't come up with a patch. Sorry but that wasn't obvious. Many people who post to this list do have some coding skills that's why I made the suggestion. Perhaps you can find somebody who can come up with a patch for you. Maybe someone is willing to do so with a small financial incentive. Some people on the list have done contract work in the past, IIRC. Just trying to help, -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
