From: malc <malc@pulsesoft.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] OpenStep / Busmouse - correct patch
Date: Tue, 3 Jan 2006 18:44:32 +0300 (MSK) [thread overview]
Message-ID: <Pine.LNX.4.61.0601031844010.1532@home.oyster.ru> (raw)
In-Reply-To: <Pine.LNX.4.63.0601031447430.9796@wbgn013.biozentrum.uni-wuerzburg.de>
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
next prev parent reply other threads:[~2006-01-03 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 18:38 [Qemu-devel] OpenStep / Busmouse - correct patch engel
2006-01-01 22:35 ` Johannes Schindelin
[not found] ` <Pine.LNX.4.63.0601012333280.32534@wbgn013.biozentrum.uni-wuerzburg.de >
2006-01-03 11:58 ` engel
2006-01-03 13:49 ` Johannes Schindelin
2006-01-03 15:44 ` malc [this message]
2006-01-03 17:47 ` engel
2006-05-15 13:53 ` Christian Brunschen
2006-05-15 15:26 ` Natalia Portillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.61.0601031844010.1532@home.oyster.ru \
--to=malc@pulsesoft.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).