9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: erik quanstrom <quanstro@quanstro.net>
Subject: Re: [9fans] realemu update
Date: Mon,  7 Mar 2011 09:19:58 -0500	[thread overview]
Message-ID: <AANLkTimdXhM30GGC4_isZ8PC9uUvXvif_oO2V+tLx2gs@mail.gmail.com> (raw)
In-Reply-To: <fe870e1024ba532cd19f1b09aaec88f1@brasstown.quanstro.net>

On Mon, Mar 7, 2011 at 7:23 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>> in /dev/realmode, you write a struct Ureg (from /386/include/ureg.h)
>> (in x86 machine byte order?) containing the register contents and the
>> interrupt number of the bios call you want to make.
>
> yes.  you should use libmach to do this dirty work.

huh?  what does libmach (which takes apart executables)
have to do with any of this?

the interface is well defined and portable: it is an x86 Ureg
struct in x86 byte order, because you are executing x86 code.

i think cinap's structuring of realemu as a file server is very
elegant, and i say that as the author of both 8i and /dev/realmode.
it's one of those things that is completely unexpected and yet
falls out quite naturally from the general plan 9 approach.
very very cool.

russ


  parent reply	other threads:[~2011-03-07 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05  6:49 cinap_lenrek
2011-03-06  7:35 ` Lucio De Re
2011-03-06 18:48   ` cinap_lenrek
2011-03-07  4:21     ` Lucio De Re
2011-03-07 10:39       ` cinap_lenrek
2011-03-07 11:07         ` Lucio De Re
2011-03-07 11:50           ` cinap_lenrek
2011-03-07 12:23         ` erik quanstrom
2011-03-07 12:39           ` Lucio De Re
2011-03-07 14:19           ` Russ Cox [this message]
2011-03-07 14:44             ` Lucio De Re
2011-03-07 15:03               ` Russ Cox
2011-03-08 10:45                 ` Stanley Lieber
2011-03-08 11:10                 ` Stanley Lieber
2011-03-08  7:42                   ` cinap_lenrek at gmx.de

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=AANLkTimdXhM30GGC4_isZ8PC9uUvXvif_oO2V+tLx2gs@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@9fans.net \
    --cc=quanstro@quanstro.net \
    /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).