Subject: Re: Well, you may be... was Re: I am happy to report...
To: David A. Gatwood <marsmail@globegate.utm.edu>
From: Bill Studenmund <skippy@macro.Stanford.EDU>
List: port-macppc
Date: 11/11/1998 13:16:28
On Wed, 11 Nov 1998, David A. Gatwood wrote:

> On Wed, 11 Nov 1998, Bill Studenmund wrote:
> 
> > So two things come to mind:
> > 
> > 1) We need to do ADB device re-addressing. Usually what happens under
> > MacOS is that the Extended Keyboard gets readdressed to addr 15.
> > 
> > This problem's not an issue for mac68k as we've always booted after MacOS,
> > which will do the re-addressing.
> 
> Sounds like you should consider borrowing (back?) the adb code from
> MkLinux, specifically adb.c, adb_keyboard.c, adb_mouse.c....  Just a
> thought.   :-)

Well, that's more a choice for Tsubai as he's working on the adb stuff and
I'm not. :-)

It would be borrowing back. :-) Though since MkLinux boots after MacOS
boots, I suspect they wouldn't see this problem as enough of MacOS would
have run to readdress one of the keyboards to some other #. It's only when
booting through Open Firmware that I think we'd run into this problem, so
only we, linuxpmac, and OpenBSD would hit it.

> BTW, are there really two keyboards or is one of them your mouse?  Or is
> there yet a third device lurking at address 2?  Just wondering....

It's part of the mouse. It's how it can do meta-key assignment under
MacOS.

As an aside, the readdressing needed here is why this mouse makes the
debugger key stop working on my IIsi. :-) The IIsi adb code only
recognizes the reset and debugger soft keys from adb address 2, not any
valid kbd. The main keyboard (with the power button) usually gets moved to
15, so things break. :-(

Take care,

Bill