From: geerten kuiper <geerten@bart.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: FW: mp.c
Date: Thu, 30 Aug 2001 21:00:12 +0200 [thread overview]
Message-ID: <3.0.1.32.20010830210012.00d9c638@pop.bart.nl> (raw)
In-Reply-To: <1070FB530C37D511967A006008F6A51456BD93@hktgv001v3.twpl.tel ecom.ptt.nl>
Jim,
>attached is a version of /sys/src/9/pc/mp.c which will perhaps
>deal with multifunction devices which share interrupt pins (pretty stupid
>when they don't have to, but that's the way it is).
>
>i can't actually test such a configuration but the code works as
>expected with single-function configurations.
>
>let me know.
This indeed solved the mp problem for me. Thanks.
Geerten.
parent reply other threads:[~2001-08-30 19:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1070FB530C37D511967A006008F6A51456BD93@hktgv001v3.twpl.tel ecom.ptt.nl>]
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=3.0.1.32.20010830210012.00d9c638@pop.bart.nl \
--to=geerten@bart.nl \
--cc=9fans@cse.psu.edu \
/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).