[sane-devel] Canon MF8030c

2010-07-26 Thread Mickael Profeta
Le Mon, 26 Jul 2010 23:01:15 +0200, Nicolas Martin a ?crit : > I think this one rocks. Good, one good news. > But it still shows the same new protocol used here ;-( > Maybe there's not too much changes to add to the actual ImageClass > protocol, but I need first to have a deeper look at the me

[sane-devel] Canon MF8030c

2010-07-26 Thread Nicolas Martin
I think this one rocks. But it still shows the same new protocol used here ;-( Maybe there's not too much changes to add to the actual ImageClass protocol, but I need first to have a deeper look at the messages, then change the code for it if I can get to understand what the frames mean. So I cann

[sane-devel] Canon Scan 3000f

2010-07-26 Thread Hawk Anonymous
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, just wanted to ask if there is any progress reagarding this typ of scanner. The last message is from 2008 and it seems to be still unsupported. I own such a device and could provide you with sniff usb logs or other information (if you tell me how

[sane-devel] HP 5590 and 5590P

2010-07-26 Thread Ian Thurlbeck
Hi there can someone confirm that the 5590P scanner WITHOUT the ADF is indeed the same as the 5590 (which has the ADF) ? In addition, a quick note of how good the support is would be great! Many thanks Ian -- Ian Thurlbeckhttp://www.mathstat.strath.ac.uk/ Mathematics and Stati

[sane-devel] Canon MF8030c

2010-07-26 Thread Mickael Profeta
Hi Nicolas, > I'm very skeptical if we can come to some success using the current > ImageClass protocol, I'm afraid a rewrite of this new protocol is > necessary. With understanding of new messages, how they are formated > and of the data they content, this requires having access to a real > devic

[sane-devel] What happens with Epson support?

2010-07-26 Thread Olaf Meeuwissen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Merging all three posts on the subject. On 2010-07-25 22:24, m. allan noah wrote: > There have been very few changes to epson backend since 1.0.19, so I > am surprised it did not work in later versions. The changes in the epson backend between 1.0.1