NetBSD Problem Report #10240

Received: (qmail 12011 invoked from network); 31 May 2000 01:39:22 -0000
Message-Id: <200005310139.SAA09628@nbwww.isc.org>
Date: Tue, 30 May 2000 18:39:22 -0700 (PDT)
From: t-horikawa@aj.jp.nec.com
Reply-To: t-horikawa@aj.jp.nec.com
To: gnats-bugs@gnats.netbsd.org
Subject: Mouse does not work
X-Send-Pr-Version: www-1.0

>Number:         10240
>Category:       port-macppc
>Synopsis:       Mouse does not work
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-macppc-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed May 31 01:40:00 +0000 2000
>Closed-Date:    Tue Mar 06 20:39:50 +0000 2007
>Last-Modified:  Tue Mar 06 20:39:50 +0000 2007
>Originator:     Takashi Richard Horikawa               Takashi Richard Horikawa
>Release:        1.4.2
>Organization:
NEC Networks Development Laboratories
>Environment:
NetBSD  1.4.2 NetBSD 1.4.2 (GENERIC) #0: Wed Mar 15 21:53:17 PST 2000     toddpw
@leia.toddpw.net:/usr/src/sys/arch/macppc/compile/GENERIC macppc
>Description:
My mouse attached to Power Macintosh 4400/200
does not work, because its access is not ams0
but ams1 whose mouse events will not reach
to wsmouse0.

Although the Apple Desktop Bus has a key board
and a mouse, NetBSD prepares akdb0, akdb1, ams0,
and ams1, as shown in the following boot messsage,
and uses akdb1 and ams1. While the key-board
events from akbd1 are designed to be passed to wskbd0
via 'akbd_cd.cd_devs[0]', the mouse events from ams1
are not deliverd to anywhere.

--------
adb0 at obio0 offset 0x16000 irq 18: 4 targets
aed0 at adb0 addr 0: ADB Event device
akbd0 at adb0 addr 2: extended keyboard
wskbd0 at akbd0: console keyboard
ams0 at adb0 addr 3: 1-button, 100 dpi mouse
wsmouse0 at ams0
akbd1 at adb0 addr 2: keyboard II (Japanese layout)
wskbd at akbd1 not configured
ams1 at adb0 addr 3: 1-button, 100 dpi mouse
wsmouse at ams1 not configured
>How-To-Repeat:
Anytime when we start to use X-window system,
e.g. by executing 'xinit', as far as my Power
Macintosh 4400/200 is concerned.

>Fix:
To fix the mouse problem, I modified the last part of 
ms_processevent()@/usr/src/sys/arch/macppc/dev/ams.c
so that the ams1 events can reach to wsmouse0 via
'ams_cd.cd_devs[0]'. So far, it works fine and produces
no bad side effect.
--------
	if (msc->sc_wsmousedev) {
		wsmouse_input(msc->sc_wsmousedev, new_event.u.m.buttons,
			      new_event.u.m.dx, -new_event.u.m.dy, 0);
	} else {
		extern struct cfdriver ams_cd;
		struct ams_softc *sc = ams_cd.cd_devs[0];

		if(sc->sc_wsmousedev)
			wsmouse_input(sc->sc_wsmousedev, new_event.u.m.buttons,
				      new_event.u.m.dx, -new_event.u.m.dy, 0);
	}
#if NAED > 0
	aed_input(&new_event);
#endif
}
--------

The following source list is the corresponding part
involved in the original 1.4.2 release.
--------
	if (msc->sc_wsmousedev)
		wsmouse_input(msc->sc_wsmousedev, new_event.u.m.buttons,
			      new_event.u.m.dx, -new_event.u.m.dy, 0);
#if NAED > 0
	aed_input(&new_event);
#endif
}
--------

>Release-Note:
>Audit-Trail:

From: Ben Harris <bjh21@netbsd.org>
To: gnats-bugs@netbsd.org, t-horikawa@aj.jp.nec.com
Cc:  
Subject: port-macppc/10240: Mouse does not work
Date: Wed, 31 Jan 2001 16:26:26 +0000 (GMT)

 A better workaround for this bug would be to use wsmux.  In your kernel
 config file, remove the existing wsmouse lines, and do:

 wsmouse* at ams? mux 0
 pseudo-device wsmux 2

 Then use /dev/wsmouse rather than /dev/wsmouse0 in your X server.

 See <URL:http://www.netbsd.org/Documentation/wscons/#muxdevices> for more
 details.

 -- 
 Ben Harris                                                   <bjh21@netbsd.org>
 Portmaster, NetBSD/arm26               <URL:http://www.netbsd.org/Ports/arm26/>


From: Makoto Fujiwara <makoto@ki.nu>
To: t-horikawa@aj.jp.nec.com
Cc: gnats-bugs@gnats.netbsd.org
Subject: Re: port-macppc/10240: Mouse does not work
Date: Tue, 07 Aug 2001 09:01:49 +0900

 T.Horikawa reported as
  | My mouse attached to Power Macintosh 4400/200
  | does not work, because its access is not ams0
  | but ams1 whose mouse events will not reach
  | to wsmouse0.

 I now have PM4400/200 and encountered to the same problem.
 The work arround I took for 1.5X is to swap ams/wsmouse
 by following 4400-dedicated-kernel.

   Just FYI,
   Makoto
 --- GENERIC	Mon Aug  6 17:24:14 2001
 +++ GENERIC-ams-swap	Tue Aug  7 08:29:33 2001
 @@ -211,7 +211,8 @@

  wsdisplay0 at ofb? console ?
  wskbd0	at akbd? console ?
 -wsmouse* at ams?
 +wsmouse1 at ams?
 +wsmouse0 at ams?

  scsibus* at adv?
  scsibus* at ahc?

 ---
 (Makoto Fujiwara)

State-Changed-From-To: open->closed
State-Changed-By: manu@netbsd.org
State-Changed-When: Wed, 17 Nov 2004 18:11:05 +0000
State-Changed-Why:
problem was fixed


State-Changed-From-To: closed->open
State-Changed-By: manu@netbsd.org
State-Changed-When: Wed, 17 Nov 2004 18:19:44 +0000
State-Changed-Why:
Ooops, it seems I did fix it on my tree but I did not commit the fix.
Let's re-open it until the fix get in tree


State-Changed-From-To: open->feedback
State-Changed-By: macallan@netbsd.org
State-Changed-When: Tue, 22 Aug 2006 05:19:02 +0000
State-Changed-Why:
has this been fixed?


State-Changed-From-To: feedback->closed
State-Changed-By: macallan@netbsd.org
State-Changed-When: Tue, 06 Mar 2007 20:39:50 +0000
State-Changed-Why:
can't reproduce this problem and feedback hasn't been provided for half a year so I'll assume it's fixed.


>Unformatted:

Home	PR Database Search