[sane-devel] Fwd: sanei_usb limitations

m. allan noah kitno455 at gmail.com
Fri Nov 26 23:10:54 UTC 2010

resend to entire list...
Reinhold Kainhofer has recently worked up a patch with an alternative
implementation of your idea- and there was some discussion about yet a
third mechanism, which relies on a 'setting' function to be called
prior to transferring the data, much as the existing timeout control
code works. I think that would be the best choice, not sure if
Reinhold has gotten a chance to work on it.


On Fri, Nov 26, 2010 at 5:00 PM, Hugo "Bonstra" Grostabussiat
<dw23.devel at gmail.com> wrote:
> Hi,
> as I said in my last post, I am writing a backend for Hercules Scan at home
> 48 USB scanner.
> This device uses an unusual USB interface which has 3 bulk endpoints:
> * EP 0x01 is used to send commands to device
> * EP 0x82 is used to get the result of some commands
> * EP 0x83 is used to get scan data
> In its current state however, sanei_usb API does not allow us to choose
> what endpoint to use for bulk transfers. It will always use the first IN
> and OUT endpoints it finds for functions sanei_usb_read_bulk() ans
> sanei_usb_write_bulk() respectively.
> To overcome that limitation, I thought of adding a few functions to
> sanei_usb API to allow specifying an alternative endpoint (for instance:
> sanei_usb_read_bulk_ep() which would take an additional ep argument of
> type SANE_Byte). It wouldn't break any existing backend.
> Would a change of that kind be accepted ? Or should I use libusb directly ?
> Thanks in advance.
> ---
> Hugo Grostabussiat
> --
> sane-devel mailing list: sane-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>             to sane-devel-request at lists.alioth.debian.org

"The truth is an offense, but not a sin"

"The truth is an offense, but not a sin"

More information about the sane-devel mailing list