All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Rydh <samuel@ibrium.se>
To: linuxppc-dev@lists.linuxppc.org, marsmail@globegate.utm.edu
Subject: Re: Mac-on-Linux
Date: Sat, 22 May 1999 19:37:19 +0200	[thread overview]
Message-ID: <19990522193719.15424@ibrium.se> (raw)
In-Reply-To: <Pine.LNX.3.96.990521213127.19285C-100000@globegate.utm.edu>; from David A. Gatwood on Fri, May 21, 1999 at 09:35:21PM -0500


On Fri, May 21, 1999 at 09:35:21PM -0500, David A. Gatwood wrote:
> 
> 
> Quick question: what is the nature of the kernel support for mac-on-linux? 
> Some folks in the MkLinux camp have been discussing writing equivalent
> 2.0.xx kernel code that works through mach.  I know that it will likely
> need to be able to map the ROMs into user space.  I also suspect that
> handling code (which could be very messy, but we'll cross that bridge when
> we get to it) and possibly the memory management code.  Beyond that, what
> other hurdles are there?

The Mac-on-Linux kernel support code has in principle the following 
tasks:

  - Emulate privileged instructions.
  - Handle the MMU (maps ROM, RAM etc.)

The implementation is primarily based upon hooks in the
low-level exception handlers. Besides this, the interaction
with the kernel has been kept at a minimum.

I believe the exception hooks must be put into the
mach kernel - possibly it is easiest to put all code 
there.

/Samuel


----------------------------------------------------------
 E-mail <samuel@ibrium.se>  WWW: <http://www.ibrium.se>
  Phone/fax: (home) +46 8 4418431, (work) +46 8 7908470   
----------------------------------------------------------

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-05-22 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19990519235050.60265@ibrium.se>
     [not found] ` <Pine.LNX.3.96.990519210752.5706A-100000@EdMcMan.Dyn.Ez-Ip.Net>
     [not found]   ` <19990520192459.17170@ibrium.se>
     [not found]     ` <19990520171823.A409@jasons.dyn.kpn.cx>
1999-05-21 15:32       ` Mac-on-Linux Stefan Berndtsson
1999-05-21 18:37         ` Mac-on-Linux Samuel Rydh
1999-05-21 20:19           ` Mac-on-Linux Stefan Berndtsson
1999-05-22  0:04             ` Mac-on-Linux Samuel Rydh
1999-05-22  2:35               ` Mac-on-Linux David A. Gatwood
1999-05-22 17:37                 ` Samuel Rydh [this message]
1999-05-23  4:11                   ` Mac-on-Linux David A. Gatwood
1999-05-22  7:15               ` Mac-on-Linux Stefan Berndtsson

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=19990522193719.15424@ibrium.se \
    --to=samuel@ibrium.se \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=marsmail@globegate.utm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.