From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EtoM9-0004D4-UN for qemu-devel@nongnu.org; Tue, 03 Jan 2006 10:45:50 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EtoM7-0004CS-QV for qemu-devel@nongnu.org; Tue, 03 Jan 2006 10:45:49 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EtoM7-0004CM-LG for qemu-devel@nongnu.org; Tue, 03 Jan 2006 10:45:47 -0500 Received: from [217.10.32.19] (helo=comtv.ru) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EtoNM-0002zb-Nc for qemu-devel@nongnu.org; Tue, 03 Jan 2006 10:47:04 -0500 Received: from av1474.oops ([10.0.66.9] verified) by comtv.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 118889461 for qemu-devel@nongnu.org; Tue, 03 Jan 2006 18:44:03 +0300 Date: Tue, 3 Jan 2006 18:44:32 +0300 (MSK) From: malc Subject: Re: [Qemu-devel] OpenStep / Busmouse - correct patch In-Reply-To: Message-ID: References: <61142.80.226.246.226.1136140727.squirrel@www.mathematik.uni-marburg.de> <53441.80.226.220.222.1136289496.squirrel@www.mathematik.uni-marburg.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, 3 Jan 2006, Johannes Schindelin wrote: > Hi, > > On Tue, 3 Jan 2006, engel@mathematik.uni-marburg.de wrote: > >> The most difficult problem was actually finding documentation on the >> busmouse controller ;-). > > That always seems to be the biggest problem... > >>> How about this on top (unfortunately untested, since I do not >>> have a system handy which supports a busmouse): >> >> Hmm, there seems to be a problem with your patch, though I haven't quite >> figured out what exactly the cause is. When using the -busmouse option, >> the busmouse_init function is called and seems to register the callbacks >> for the provided I/O address ranges successfully (return value is 0 from >> register_ioport_{read,write}) - but the actual callback routines are >> never being executed, which results in OpenStep not recognizing the >> busmouse. > > I'll investigate. > FWIW. IRQ 5 is already taken by sb16. -- mailto:malc@pulsesoft.com