Re: [hpoj-devel] 2.4.0 kernel issues

[Burkhard K. <bu...@bu...>]

David Paschal
> 
> All I see in your 2.4 debug output is an open of the scan channel immediately
> followed by a close.  I assume this output corresponds to the SANE+PTAL
> output you sent on September 20.  In that case, we saw a successful open,
> and the write() of two bytes (the SCL "Esc-E" reset command) failed (returned
> -1), so the SANE backend had no choice but to give up and close the channel.
> I would suggest examining the code path taken by writes (see mlc_sendmsg()).
> Perhaps there's a mismatch in the mlc_proto_ops structure.  You could also
> try hacking the PTAL_LOG_DEBUG statement around line 884 of ptal/ptal.c so
> it also prints the value of errno.
> 
> Looking back at Damcha's original message reporting compile problems with
> 2.4, there were warnings about initializing mlc_proto_ops:
> > ieee12844.c:1541: warning: initialization from incompatible pointer type
> > ieee12844.c:1542: warning: initialization from incompatible pointer type
> > ieee12844.c:1545: warning: initialization from incompatible pointer type
> > ieee12844.c:1547: warning: excess elements in struct initializer
> > ieee12844.c:1547: warning: (near initialization for `mlc_proto_ops')
> Line 1542 is for mlc_sendmsg and 1543 is for mlc_recvmsg, so it's obviously
> a mismatch in this table that's causing writes to fail.
That would be too easy. As I wrote in my posting accompanying my patch
I have already taken care of that. After applying my patch, the module
compiles without any such warnings. I just double checked, all pointer
assignments to the mlc_proto_ops structure are in alignment with 
the definition of this structure in net.h.

Burkhard

-- 
Burkhard Kohl			Tel/FAX: +49 30 698 15 905
Melchiorstr. 8			bu...@bu...
10179 Berlin