On Thu, 7 Dec 2006, Ren? Kjellerup wrote: > So the primary question is, which endpoint does > one write to, and which does one read from?
the in/out identifiers are written from the perspective of the host, not the device. so you read in and write out. just as a check, the IN endpoint will have its high bit set (0x80). it is not unusual to get timeout errors and other weirdness on your first command to the device, some fujitsu scanners require you to call TEST UNIT READY several times with a really short timeout and ignore the errors before they will play. allan -- "so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls" - Max Cavalera From [email protected] Fri Dec 8 17:37:31 2006 From: [email protected] (Franz Bakan) Date: Fri Dec 8 17:38:12 2006 Subject: [sane-devel] 3 minor problems with current (20061202) CVS code on OS/2 In-Reply-To: <20061208004504.47c56cc6@inspiron> Message-ID: <[email protected]> On Fri, 8 Dec 2006 00:45:04 +0100, Alessandro Zummo wrote: > > now all compiles again here on OS/2 without errors. > > great! now tell me you have an epson scanner to test > the driver with :) Well which epson scanners are supposed to work? there is no epson2.desc or epson2.man. I have an epson GT-9500 I could try later this weekend. What's the benefit over epson backend? Perhaps I should have tried the mailing-list archive for an answer first. Best regards Franz
