Hi,
I have attached three patches for the xerox_mfp driver. The first one is
for general support of the Samsung SCX-4521F scanner. The second is some
minor code cleanup only. The last one fixes some (general?) issue for
the driver in halftone and lineart mode.
I have tested the new driver
Alright, here it is on a silver platter :-)
Hi,
after some two years of struggling with Samsung's proprietary driver for my
CLX-2160 MFP, I've finally come accross the xerox_mfp module and it works very
nicely! So far I've not experienced any of the instabilities and conflicts
with the splix printer driver that happened with Samsung's
2011/3/9 ABC abc at telekom.ru
| for (tr = available_transports; tr-ttype; tr++) {
|
|DBG (4, %s: %s: tr-ttype=%s\n, __FUNCTION__, devname, tr-ttype);
|
|if (!strncmp (devname, tr-ttype, strlen(tr-ttype)) ||
|(!strncmp (devname, libusb, strlen(libusb))
| !strncmp
2011/3/9 Warren Turkal wt at penguintechs.org:
2011/3/9 ABC abc at telekom.ru
?What i think should actually happen is that sanei should have it's own
method for dealing with usb (and other busses) in whatever form it takes
(e.g. /dev/scanner dev file or libusb or scsi device or whatever).
On Wed, Mar 9, 2011 at 11:46 AM, m. allan noah kitno455 at gmail.com wrote:
2011/3/9 Warren Turkal wt at penguintechs.org:
2011/3/9 ABC abc at telekom.ru
What i think should actually happen is that sanei should have it's own
method for dealing with usb (and other busses) in whatever form
Responses below.
On Tue, Mar 8, 2011 at 1:13 AM, m. allan noah kitno455 at gmail.com wrote:
Thanks for the patch. I must confess I don't quite understand the
code.
A lot of the lines of code just added debugging output so that I could
see what functions were being called as I find the code
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.
The author was responding to bug reports yesterday, so I think it's a
bit early for you to be pessimistic :)
allan
--
The truth is an offense,
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.
On Tue, Mar 8, 2011 at 1:23 PM, m. allan noah kitno455 at gmail.com wrote:
The author was responding to bug reports yesterday, so I think it's a
bit early for you to be pessimistic :)
This is a fair point.
wt
-- next part --
An HTML attachment was scrubbed...
URL:
I have a small patch that works around a bug in the xerox_mfp driver.
It is attached.
The bug boils down to the following. The devname generated by the
sanei code is libusb instead of usb. I think that this may stop
the xerox_mfp backend from working on any system using libusb to talk
to a USB
Thanks for the patch. I must confess I don't quite understand the
code. If the caller provides a device name which does not exactly
exist, I think the backend should just return an error, instead of
trying to find a similarly named device. There is no guarantee that
device names will have a
Hello.
I want to modify backend/xerox_mfp.c to allow colour scanning (scan_modes
and scan_mode_to_code arrays), and also backend/xerox_mfp.conf.in (in order
to support workcentre 3210 and workcentre 3220).
Where should I send the patch?
Bye.
-- next part --
An HTML
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
I've successfully used my multifunction Samsung SCX4725-FN with the xerox_mfp
backend.
On lower resolutions (75-200 dpi) the colors seem to be off (e.g. b/w drawing
shows colored lines instead of black lines)
300 and 600 dpi are fine.
Both flatbed and automatic document feeder work fine.
I'll
15 matches
Mail list logo
