Youry,
That code was submitted by SAMSUNG developer(s). I will forward your
email to them.
-abc
On Wed, Aug 09, 2017 at 01:42:45AM +0300, Youry Metlitsky wrote:
>
> On WorkCentre 3515 dev->compressionTypes is 0x51 and (dev->compressionTypes &
> (1 << 6)) is true.
device may be damaged (or somehow lost calibration) after
transportation.
Test the scanner in Windows on desired resolutions. If it does not have
have same problem under Windows, test again under Linux if problem
persists. Please report your findings.
-abc
On Mon, Jan 23, 2017 at 07:50:12PM +0100
which impact could be mitigated with open() with O_EXCL flag. (Or
fopen() with "x" flag, but I don't know how portable it's again.) In
that regard, mktemp() can not be worse than opening static filename,
like pieusb_specific.c, avision.c, canon630u-common.c, pnm.c,
xerox_mfp.c are currently do
Hello,
To what mktemp() should be replaced? Will there be sanei function to
drop-in replace it?
On Wed, Sep 21, 2016 at 10:12:27PM +0900, Olaf Meeuwissen wrote:
> Looking over the build log (love how clean those compile commands look,
> BTW), next are four linker warnings about the use of
ve not done much testing, but it would help potential users.
Xerox WorkCentre 3225 is not listed as supported by SANE, afaik.
-abc
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail w
/20131024160645019/uld_v1.00.06.tar.gz
I just downloaded for a test: 16090900 Nov 8 2013 uld_v1.00.06.tar.gz
sha1sum: a7890a6cd1b9d814d6ce7a5499ee7a4e4abf905d uld_v1.00.06.tar.gz
-abc
On Mon, Nov 03, 2014 at 10:00:48AM -0500, m. allan noah wrote:
you have to broaden your search, I think
Hello James,
scanimage --help should show all available options. And by default it
should not chop anything. Maybe scanner is miscalibrated on the factory
or something is shifted after rough device transportation.
-abc
On Mon, Jun 16, 2014 at 01:21:49AM -0700, James Patterson wrote:
Hello
seeing only one device at 3:005:3/3:005:4 (and that target
fails),
but smfp sees two, and first one (at 3:005:1/3:005:2) is actually working
correctly.
Need help of some usb expert at this point.
-abc
On Mon, Jul 22, 2013 at 10:33:58PM +0200, Alex Eftimie wrote:
On Mon, Jul 8, 2013 at 10:39 AM
Hello Guennadi Liakhovetski,
On Sun, Jul 14, 2013 at 05:34:02PM +0200, Guennadi Liakhovetski wrote:
Except - 600
dpi colour produces broken images with stairs - some image stripes are
repeated vertically.
Maybe you could show image sample.
-abc
Alex Eftimie,
On Sun, Jun 30, 2013 at 01:56:08PM +0300, Alex Eftimie wrote:
On Sun, Jun 30, 2013 at 1:31 PM, ABC abc at telekom.ru wrote:
It maybe be becasue (it is possible) that smfp using different scanning
mode, like different resolution. (And then doing some image conversion
John Paul Adrian Glaubitz,
SCX-3400 model is already in the upstream. But it is marked
as untested. If it's actually tested please report. And, AFAIK
libsane.rules is don't need to be edited because it is
autogenerated (somebody correct me if I'm wrong).
Thanks,
-abc
On Fri, Jul 05, 2013 at 09
the proprietary drivers from
... but the usb problem remains.
Did you mean there is different usb problem with smfp driver? And what
was usb problem with xerox_mfp?
-abc
On Sun, Jun 30, 2013 at 12:15:22PM +0300, Alex Eftimie wrote:
On another note, do you know why the smfp: protocol
Alex,
On Sun, Jun 30, 2013 at 01:56:08PM +0300, Alex Eftimie wrote:
On Sun, Jun 30, 2013 at 1:31 PM, ABC abc at telekom.ru wrote:
It maybe be becasue (it is possible) that smfp using different scanning
mode, like different resolution. (And then doing some image conversion
internally
at 2011-02-13 which fall into bug date range).
-abc
On Sat, Jun 02, 2012 at 06:27:53AM +0200, Rogan Dawes wrote:
[xerox_mfp] list_one_device: libusb:001:006
No scanners were identified. If you were expecting something different,
Your logs does not show communication of driver with the device.
If you able to change that, do not even touch sane-find-scanner,
concentrate on scanimage -L.
-abc
On Thu, May 31, 2012 at 05:23:19PM +0200, Rogan Dawes wrote:
scanimage -L, however, fails to identify this device:
root at gw
Hello,
Try to change your udev rules:
ATTRS{idVendor}==0x04E8, ATTRS{idProduct}==0x3441,
ENV{libsane_matched}=yes
Report if scanner is detected and working ok pls.
-abc
On Fri, Dec 30, 2011 at 11:21:53AM +0600, ??? wrote:
For Samsung SCX-3205W driver needed xerox_mfp. So write all
I will not help you on that. Please read
http://www.sane-project.org/contrib.html
-abc
On Sat, Nov 12, 2011 at 06:29:29PM +0300, Ilya Tumaykin wrote:
I have no /proc/bus/usb, but here are the rest of the info I collected. Not
sure if I should add these files as attachements, so I uploaded
:
http://www.meier-geinitz.de/sane/misc/develop.html
+ http://www.sane-project.org/backend-writing.txt
Good bye. :)
-abc
On Sun, Nov 13, 2011 at 02:47:55PM +0300, Ilya Tumaykin wrote:
You mean I should step forward from Reporting Unsupported Scanners to the
next section Writing a Backend and start
of adding unsupported device:
http://www.meier-geinitz.de/tinc?key=rDoQ7lrjformname=adddev
(Not sure how useful is this though.)
-abc
On Sun, Nov 13, 2011 at 04:10:51PM +0400, ABC wrote:
Hello Ilya,
I mean someone else can tutor you, but not me. Sorry. I only
participated becasue
Hello Ilya Tumaykin,
Then you should go standard/hard way:
http://www.sane-project.org/contrib.html
-abc
On Fri, Nov 11, 2011 at 01:30:32AM +0300, wrote:
Thanks for your reply.
Of course I've already tried that with no luck at all.
The short story of things that already
Hello Ilya,
Try to add USB ids of your device to your xerox.conf
and try scanimage -L
-abc
On Thu, Nov 10, 2011 at 10:44:54PM +0300, wrote:
Hello everyone.
I am a long time Linux user and Samsung SCX-4100 owner. In ancient times
SANE didn't have support for my model
2011-10-17 12:22 JAZunwanted files removed
2011-10-17 12:00 JAZApplied patch for HPN6310
These patches effectively removing applied by me at 2011-10-01 (two week
before 2011-10-17). Which si bad.
git log -p backend/xerox_mfp.conf.in
Thanks. Added into git.
To list:
Btw, now it doesn't regenerate Lists of Devices on commit? I don't see
new divice on
http://www.sane-project.org/lists/sane-backends-cvs.html#S-XEROX-MFP
On Tue, Jun 14, 2011 at 10:55:31PM +0200, Malte Starostik wrote:
From: Malte Starostik m-starostik at
Ah.
Strangely I didnt' receive sane-devel from May 20 til Jun 8.
On Thu, Jun 16, 2011 at 06:32:27AM -0400, m. allan noah wrote:
yes- see recent thread on this list titled: 'Alioth server upgrades'
allan
On Thu, Jun 16, 2011 at 5:42 AM, ABC abc at telekom.ru wrote:
Thanks. Added into git
Hello,
This is accidental bug introduced just before 1.0.21 release, it is
already fixed at 2010-05-03. Your fix is incorrect.
Best regards.
On Sun, Apr 03, 2011 at 01:17:56AM +0400, Boris Samorodov wrote:
Hi List,
On Sat, 02 Apr 2011 11:16:54 +0400 Boris Samorodov wrote:
I've got a
Turkal wrote:
2011/3/9 ABC abc at telekom.ru
On Wed, Mar 09, 2011 at 08:55:26AM +, Warren Turkal wrote:
I use vim. I use a different default tab width.
I use default. I think if you able to costomize Vim to non-defualt
setting, then you are able to resolve consequences
I will correct the bug.
Device string is parsed for network scanner support.
On Tue, Mar 08, 2011 at 08:23:43AM -0500, m. allan noah wrote:
I am familiar with sanei_usb device detection, and I speak diff. The
only thing that seems odd is just why the backend is parsing the
device strings.
Send patch to _latest_ version of SANE (from git repository) to me.
How to obtain latest version: http://www.sane-project.org/cvs.html
You can send USB ids to me.
On Wed, Sep 29, 2010 at 12:18:22PM +0300, Navolochka Maksim wrote:
Hello.
I want to modify backend/xerox_mfp.c to allow colour
Probably problem is in usb halting.
I did simple sanei_usb_clear_halt() on open and closing device.
But maybe this is somewhat wrong. It was worked excellent for me.
Unfortunalely I'm not usb guru and can not guess solution.
ABC
On Tue, Jun 01, 2010 at 10:16:23AM -0300, elejota at lavabit.com
On Tue, May 19, 2009 at 04:43:43PM +0100, Michael Whapples wrote:
It appears that using the xerox_mfp driver scanadf doesn't detect
the paper state in the document feeder
I think it is scanadf feature that it doesn't detect paper state, it
just scans as much as it can, under divice error. And
On Tue, May 19, 2009 at 08:34:04PM +0400, ABC wrote:
On Tue, May 19, 2009 at 04:43:43PM +0100, Michael Whapples wrote:
It appears that using the xerox_mfp driver scanadf doesn't detect
the paper state in the document feeder
I think it is scanadf feature that it doesn't detect paper state
There is nothing which might obviously be a Xerox proprietary backend;
nothing with xerox in the name; nothing beginning with 'x'.
I believe Xerox used Samsung driver with name smfp.
Thanks. Added it into conf and desc.
On Mon, Mar 16, 2009 at 01:17:13AM +0100, Aleksandar Popadi?? wrote:
I'm happy to report that my Xerox works with the xerox_mfp backend. Here
is the info from lsusb about the device:
On Sun, Feb 01, 2009 at 10:41:32AM +0100, Julien BLACHE wrote:
Other than that, the backend is conflicting with usblp to claim the
USB device; do you have a way to fix that? Would going over the
emulated parallel port be possible?
Strangely, as I'm using standard SANE interface to
There is possibility that some of Samsung MFP devices could work with
xerox_mfp backend.
On Sat, Jan 17, 2009 at 10:57:36AM +0100, Julien BLACHE wrote:
Vladimir Koutny vlado at sane.ksp.sk wrote:
I already have a stand-alone app which can scan any area, in any
resolution and any color
, 2009 at 11:33:11AM +0100, Julien BLACHE wrote:
ABC abc at telekom.ru wrote:
There is possibility that some of Samsung MFP devices could work with
xerox_mfp backend.
That'd be great. I have a Dell 1815dn MFP that's just a rebadged
Samsung, and I'd be more than happy to get rid
On Thu, Dec 11, 2008 at 04:06:24PM -0500, m. allan noah wrote:
On Mon, Dec 1, 2008 at 10:23 PM, ABC abc at telekom.ru wrote:
First of all sanei_usb_init() is not designed to be used for rescanning
after any other sanei_usb functions is called. It is just initialization
and rescanning
On Thu, Dec 11, 2008 at 04:36:47PM -0500, m. allan noah wrote:
However, sanei_usb_init() is only
called by backends in sane_init() and sane_get_devices(). A frontend
will only call sane_init() once, so that is not a problem, and the
sane standard says this about sane_get_devices():
The
I got that too before:
sane-devel at lists.alioth.debian.org... Deferred: 451 Could not complete
sender verify callout
That is just aggressive spam checking. Solution was to set in muttrc:
set envelope_from=yes
On Thu, Dec 11, 2008 at 10:19:10AM -0700, mustek at ariplex.com wrote:
m.
On Thu, Dec 11, 2008 at 10:41:42AM -0700, mustek at ariplex.com wrote:
I got that too before:
sane-devel at lists.alioth.debian.org... Deferred: 451 Could not complete
sender verify callout
I received nothing at all. So I had no idea what happened. From my emails
(not to the list,
SANE_Hi!
On Wed, Dec 03, 2008 at 09:34:29PM +0100, Alessandro Zummo wrote:
On Wed, 03 Dec 2008 21:20:58 +0100
Julien BLACHE jb at jblache.org wrote:
Alessandro Zummo azummo-lists at towertech.it wrote:
Now that we have ANSI C types for everything,
it might be useful to switch.
Btw, what the point of having these typedefs?
(Besides obscurity and advertising of course).
typedef unsigned char SANE_Byte;
typedef int SANE_Word;
typedef SANE_Word SANE_Bool;
typedef SANE_Word SANE_Int;
typedef char SANE_Char;
typedef SANE_Char *SANE_String;
typedef const SANE_Char
Sorry for my curiosity.
What is the point of having in sanei_usb these two functions?
(Besides misuse of course.)
Because, sanei_usb_open is already claiming correct interface after
its opening, it is mandatory (for libusb).
Plus, there is no way to know correct interface number to claim under
trying to code it right way,
but later you realize it's don't work like this, at least for usb.
On Tue, Dec 02, 2008 at 08:14:13AM +0900, Olaf Meeuwissen wrote:
m. allan noah kitno455 at gmail.com writes:
On Mon, Dec 1, 2008 at 12:10 AM, ABC abc at telekom.ru wrote:
http://www.sane
http://www.sane-project.org/html/doc012.html
4.3.3 sane_get_devices
...
This function can be called repeatedly to detect when new devices
become available.
Nice writing but it is not possible with usb now, because sanei usb
infrastructure get list of devices only when sanei_usb_init() is
While digging in sanei sources (cvs head) I stumbled on this line:
532 #ifdef HAVE_USBCALLS
533 /* Check for devices using OS/2 USBCALLS Interface */
...
575 if (pDevDesc-bDeviceClass = USB_CLASS_VENDOR_SPEC)
576{
577 found = SANE_TRUE;
578
46 matches
Mail list logo
