qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] proprietary MIPS based ASIC
Date: Thu, 26 Oct 2006 12:28:13 -0400	[thread overview]
Message-ID: <200610261228.13529.rob@landley.net> (raw)
In-Reply-To: <200610261331.47109.paul@codesourcery.com>

On Thursday 26 October 2006 8:31 am, Paul Brook wrote:
> > How hard it is going to be to emulate
> > full system like this ? Any examples/tutorials where to start ? Any
> > experience of porting QEMU to other platforms ? Let's say MIPS+DDR+simple
> > interrupt controller and no other peripherals
> 
> I suggest you look at the existing targets. e.g. the existing mips and ARM 
> targets. IMHO it's not that hard to add new boards.

The tech docs at http://www.qemu.org/user-doc.html could really use some more 
information on this area.

The "hw" directory contains both definitions of individual pieces of hardware 
(such as i8259.or ide.c) and motherboards that integrate lots of pieces of 
hardware together (pc.c or integratorcp.c).  They're treated as 
interchangeable, both of them are initialized with a function ending 
in "_init", and there's no easy way to distinguish between them except by 
inspection.  (I could easily be wrong about this, but if so I haven't found 
the pattern or documentation yet.)

Rob
-- 
"Perfection is reached, not when there is no longer anything to add, but
when there is no longer anything to take away." - Antoine de Saint-Exupery

  reply	other threads:[~2006-10-26 16:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26  7:50 [Qemu-devel] proprietary MIPS based ASIC larytet.39605663
2006-10-26 12:31 ` Paul Brook
2006-10-26 16:28   ` Rob Landley [this message]
2006-10-26 18:28 ` Stefan Weil

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=200610261228.13529.rob@landley.net \
    --to=rob@landley.net \
    --cc=paul@codesourcery.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).