All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Hopely <phil@ayrnetworks.com>
To: William Jhun <wjhun@ayrnetworks.com>
Cc: "John D. Davis" <johnd@stanford.edu>,
	Debian MIPS list <debian-mips@lists.debian.org>,
	SGI MIPS list <linux-mips@oss.sgi.com>
Subject: Re: Replacing the Console driver
Date: Wed, 25 Jul 2001 16:45:28 -0700	[thread overview]
Message-ID: <3B5F5A18.F94328CB@ayrnetworks.com> (raw)
In-Reply-To: Pine.LNX.4.21.0107251604280.12368-100000@earth.ayrnetworks.com

William Jhun wrote:

> Hi Phil :o),
>
> The only problem with pure emulation is writing a good emulator for an
> MMU. I wrote a SPARC V8 instruction set emulator a year ago and stopped
> around the time I had to face the fact that a direct virtual->physical
> mapping would no longer be of any use. (also the semester started again
> :o). Not that it's not possible, but it's difficult and would require a
> mapping with every memory access (being very slow). However, a little
> creative help from the kernel and some creative mmap()ing might do the job
> (you can request a specific linear address with mmap()). If anyone knows
> some good methods for doing this, please inform! (and I might finish that
> emulator :o)
>
> William
>

:)  yep, you are right - the r3000 core in the mame sources I am perusing do not
implement an mmu
(the playstation and williams standups use "a custom r3000a by LSI Logic" - see
src/cpu/mips/mips.c - no cache mechanism either).

Poking around the mame sources (I've got xmame b13 r1 - ancient really, from sometime
late 1999 I think), it appears that the z180 cpu is the only core that has some kind
of mmu emulation.  The z8k & m68k also have mmu instructions, but those were not
emulated in this version of mame...

I haven't checked more recent versions, but I think recent mess (uses same cpu cores
as mame) supports early macs, so there may be an implementation example there?..


Phil


>
> On Wed, 25 Jul 2001, Phil Hopely wrote:
>
> >
> > I do not know if you have examined any of the current open source emulation
> > projects that exist, but I believe
> > you might be interested to examine www.mame.net or mess.emuverse.com?
> >
> > They have a cpu core for mips emulation, I believe it may only be r3000
> > though?..
> >
> > Also, there exist numerous open-source playstation emulators, which I believe
> > are r3000 based too...
> >
> > The mame & mess projects are matured open-source projects that have been ported
> > across the universe, they're really pretty cool, this work would be a likely fit
> > with the mess project.
> >
> > If you implement by way of pure emulation, you'd not need to change the kernel
> > at all?
> >
> > Phil
> >
> > "John D. Davis" wrote:
> >
> > > I am modifying the linux kernel to be able to be run by a simulator.  I
> > > need to modify the console driver and interrupt handler.  I have been
> > > going through the various files, console.*, tty.* and the serial files to
> > > see how to interface to the console.  I have also read some kernel korner
> > > articles, but they seem a little out of date.  Is there any other
> > > recommended documentation on the console driver and how it works on an
> > > indy? I am trying to sort out the low-level interfaces from the
> > > higher-level ones.  I just need to change the low-level interface from
> > > using the hardware to using the simulator interface.
> > >
> > > thanks,
> > > john
> > >
> > > --
> > > To UNSUBSCRIBE, email to debian-mips-request@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >

  reply	other threads:[~2001-07-26  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25 21:32 Replacing the Console driver John D. Davis
2001-07-25 22:10 ` Phil Hopely
2001-07-25 23:12   ` William Jhun
2001-07-25 23:45     ` Phil Hopely [this message]
2001-07-26  7:39 ` Geert Uytterhoeven
     [not found] <no.id>
2001-07-26  0:20 ` Alan Cox
2001-07-26  0:20   ` Alan Cox
2001-07-26  1:32   ` Ralf Baechle
2001-07-26  1:51     ` William Jhun

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=3B5F5A18.F94328CB@ayrnetworks.com \
    --to=phil@ayrnetworks.com \
    --cc=debian-mips@lists.debian.org \
    --cc=johnd@stanford.edu \
    --cc=linux-mips@oss.sgi.com \
    --cc=wjhun@ayrnetworks.com \
    /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.