At 1:38 Uhr +0200 04.05.1998, Colin Wood wrote:
>Hauke Fath wrote:
>> A kernel from 980502 sources configured with the adbdirect driver sees the
>> mouse  but not the keyboard (tried with two different kbds).
>>
>> adb0 at obio0 (ADB event device)
>> adb: using II series hardware support
>> adb: ADBReInit complete
>> adb: 100 dpi mouse at 3
>
>How recently does the breakage occur?  Does an April -current kernel show
>the same behavior?  Nothing should have changed in the ADB driver
>lately....

Looking through my out box, I see I have reported a lock-up for the
ADBDIRECT driver on 19 Mar. That was 1.3E, too. I sticked with the 1.3B
kernel then.

The Q700 is a bit special in that it has 68MB RAM, but that doesn't affect
the 1.3B kernel.

???

	hauke


>Delivered-To: hauke@Espresso.Rhein-Neckar.DE
>X-Sender: hauke@espresso.hf.org
>Mime-Version: 1.0
>Date: Thu, 19 Mar 1998 00:44:13 +0100
>To: port-mac68k <port-mac68k@NetBSD.ORG>
>From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
>Subject: ADB quirks
>Sender: port-mac68k-owner@NetBSD.ORG
>Precedence: list
>Delivered-To: port-mac68k@NetBSD.ORG
>
>Hi,
>
>a few observations from a kernel compile session this evening...
>
>[The machine in question is a Quadra 700/33/68MB]
>
>
>1) With the ADB direct-to-metal driver, the box locks up solid during the
>initial probe. This ran fine until 1.3B.

[...]

>3) The ROM based (MRG) ADB driver unconditionally disables the adb device
>if you boot with serial console -- no local X server. I can see situations
>where this comes in handy, but please make it an option (for the booter?).


--
"It's never straight up and down"     (DEVO)