(Yeah, ok, so I'm a little behind in reading mail!)

Colin Wood wrote:
> 
> Xiamin Raahauge wrote:
> >
> > Thanks to the advice of Colin Wood and Alan Briggs, I switched to a HWDIRECT
> > kernel. Now I can reinit adb at will! Muahahaahahahah!
> > Here's the dark side to this new found power. This is the message I got while
> > booting:
> > mrg: 'Quadra/Centris ROMs' ROM glue, tracing off, debug off, silent traps
> > mrg: I/O map kludge for ROMs that use hardware addresses directly.
> > adb: using II series hardware support
> > adb: cleanup: nothing returned
> > adb: ADBReInit complete
> > adb: adjustable keyboard at 2
> > adb: extended mouse <LT\^C> 0-button 3539 dpi unknown device at 3
> > adb: misc. device (remote control?) (2) at 7
> 
> I see the same thing (well, something similarly strange) on my Q700 using
> a Logitech Mouseman.
> 
> > That mouse dpi seems to be a tad bit off. Also, I have just noticed that the
> > third mouse button, which worked with MRG_ADB, no longer works. The mouse in
> > question is a Logitech TrackMan Marble.
> 
> Yeah, that's pretty much what I got.
> 
> > Here is what I got running my adb reinit program (from dmesg):
> > adb: using II series hardware support
> > adb: cleanup: nothing returned
> > adb: ADBReInit complete
> > adb: adjustable keyboard at 2
> > adb: extended mouse <LT> 0-button 566 dpi unknown device at 3
> > adb: misc. device (remote control?) (2) at 7
> >
> > The dpi is different!!!

> I definitely think the erroneous dpi is a result of timing problems with
> the HWDIRECT code.  Maybe John's latest code will perform better.  You
> might try downloading his latest HWDIRECT patches off of Puma and seeing
> if they help things...

I don't think this is a timing issue on the ADB's part. Most likely the
ADB "packet" is received correctly, but the information reported back is
not recognized, so it defaults to thinking the mouse is simply an
extended mouse, and mis-interprets the dpi/button info.

The earlier HWDIRECT kernels (356, for example), probably did not have
all the most recent "detection" code for this mouse type that had been
put into -current.

Have either of you tried a 1.3_alpha kernel, which should have all the
HWDIRECT fixes AND the code that detects more ADB device types properly?

	--John