From: Fabrice Bellard <fabrice@bellard.org>
To: Alexander Voropay <a.voropay@equant.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: Fw: [Qemu-devel] MIPS: UART access w/o -kernel option
Date: Sun, 14 May 2006 20:23:13 +0200 [thread overview]
Message-ID: <44677591.8010200@bellard.org> (raw)
In-Reply-To: <04f001c675cd$89da7a20$e90d11ac@spb.in.rosprint.ru>
Alexander Voropay wrote:
> I'm thinking about adding a new MIPS platform to the Qemu:
> http://www.linux-mips.org/wiki/Mips_Malta
>
> The Malta is very popular reference platform for the MIPS development.
> There is a special Linux MIPS/Malta kernel. Montavista and many
> other companies are offering a MIPS Malta distributives with
> pre-compiled kernels. There is a NetBSD port to the Malta.
> VxWorks/Malta exists, e.t.c.
>
> The Malta architecture is very similar to the current Qemu MIPS
> machine but the ISA addresses are different. Additionally, it
> has a PCI subsystem, so it should be possible to use existent
> Qemu PCI devices in the future. Malta has an standart PC ISA
> devices (inside the PIIX4 chip). The Qemu contains all necessary
> parts to introduce a new platform (except Galileo PCI).
>
> Fabrice, is it difficult to add a new MIPS Malta platform
> to the MIPS Qemu ? Could you add at least a framework
> for this platform (CLI options, initial .c files) ?
> P.S.The MIPS BIOS/kernel donload code should be reusable
> for the any MIPS platforms.
Adding the Malta machine support would be very interesting. You can just
copy the file mips_r4k.c to malta.c and modify it to add the missing parts.
Fabrice.
prev parent reply other threads:[~2006-05-14 18:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <28c301c6741e$e9ce2540$e90d11ac@spb.in.rosprint.ru>
[not found] ` <4463A949.9080401@bellard.org>
2006-05-12 14:08 ` Fw: [Qemu-devel] MIPS: UART access w/o -kernel option Alexander Voropay
2006-05-14 18:23 ` Fabrice Bellard [this message]
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=44677591.8010200@bellard.org \
--to=fabrice@bellard.org \
--cc=a.voropay@equant.ru \
--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).