Re: HID issues.

[Vojtech P. <vo...@su...>]

On Sat, Jan 26, 2002 at 08:13:26PM +0100, Bj|rn Augustsson wrote:
> Quoting Vojtech Pavlik <vo...@su...>:
> > On Fri, Jan 25, 2002 at 02:03:34AM +0100, Bj|rn Augustsson wrote:
> > > Sorry for the confusion.
> > 
> > You mean when we time out? Well, yes, then we have a problem. But the
> > timeout is the error case which shouldn't happen. Otherwise, I don't see
> > how any pending 'get report' requests could stay in the queue - we wait
> > for both the control and out queue to clear completely. 
> 
> Don't really know, but I do get output from the "hid_dump_input"
> function after hidinput_connect() has been called (ie too late) every
> now and then, and there's definetly something weird going on there,
> because sometimes I get weird data in them as well, as in
> 
> Jan 17 20:14:39 as22-3-7 kernel: hid-debug: input 6e69.4c20 = 1
> 
> Or some other random-looking value. Oh well.
> 
> > > > And it waits for all the
> > > > report to arrive then - it waits till the queue is empty. Maybe we are
> > > > each reading a different version? I'm looking at the current CVS.
> > > 
> > > Well, I'm not, but fairly close (CVS version tag 1.35).
> > 
> > Maybe update, there was a serious rewrite of that part.
> 
> I'm trying! :)
> 
> I haven't gotten anything since that to build and boot, that's all...

Use 2.5.2-dj6 if you can, that's probably the easiest (and working as
well).

> > Both input and feature reports come over the control pipe. The input
> > interrupt pipe isn't open at that time yet, and thus no reports are
> > coming over it.
> 
> Ah, OK. Well, that sorts that out. The problem must be somewhere else
> then.

If you find any possible reason for it, tell me, I'll take a look.

-- 
Vojtech Pavlik
SuSE Labs