Once upon a time (on Sunday 22 September 2002 09:12), Jaeger, Gerhard wisely
wrote:
> No problems here with that test program! But you should run this one
> as root user.
Yes, ran as root. Segfaults. I've investigated in the code, and it really
crashes when trying to access the first device of
On Sunday, 22. September 2002 02:28, Yann E. MORIN wrote:
[SNIP]
> OK. In dmesg, the device identifies itself as VID/PID:0x4a9/0x220D, that is
> the same as a N670U. So the chip inside ought to be the same (or
> compatible). After some digging, I came up with these results: N676U scans
> at 48 bits
--Boundary-00=_TADTQDO6ABLCA9CNND8L
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
On Saturday 21 September 2002 12:49, you wrote:
> the chip inside should be a merlin LM9832 or 9833. I currently
> bought a Canon N670U which should be compatible with
Hi there,
the chip inside should be a merlin LM9832 or 9833. I currently
bought a Canon N670U which should be compatible with the N676U
and will try an integrate it into the Plustek backend so far.
I'm not sure if the patch will make it into SANE 1.0.9 but I'm rather
optimistic...
Stay tuned
Ge
Hi,
On Fri, Sep 20, 2002 at 08:45:27PM +0200, Yann E. MORIN wrote:
> I've just had a brand new Canon CanoScan N676U. I hope it works great as it
> is not yet supported by Sane. That's why I volunteer to add support for this
> device in Sane.
>
> Could someone please point me to documents / source
Hi all!
I've just had a brand new Canon CanoScan N676U. I hope it works great as it
is not yet supported by Sane. That's why I volunteer to add support for this
device in Sane.
Could someone please point me to documents / source code / URLs / RFC /
whatever is of interest to start coding a new ba
