From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: QEMU configuration files
Date: Sat, 21 Jun 2008 11:43:57 +0300 [thread overview]
Message-ID: <f43fc5580806210143v23d5052eydc8ae162798754a@mail.gmail.com> (raw)
In-Reply-To: <485BAC6C.6070306@bellard.org>
On 6/20/08, Fabrice Bellard <fabrice@bellard.org> wrote:
> Hi,
>
> I have just updated the config file patch at
> http://bellard.org/qemu/patches . Now all targets are supported. There is a
> small documentation in config.txt.
Seems to work for Sparc. About buses, maybe the config file syntax
used in TME gives some ideas:
board0: tme/machine/sun4 name Calvin
cpu0 at board0: tme/ic/cy7c601 fpu-type tms390-c602A fpu-compliance
partial fpu-incomplete trap
sbus0: tme/generic/bus size 4GB slot-addr 0xf8000000 slot-size 32MB
slot 0 slot 1 slot 2 slot 3
sbus0 controller at board0 sbus
alias mainbus0 sbus0
ram0 at mainbus0 addr 0x0: tme/host/posix/memory ram 16MB
rom0 at mainbus0 addr 0xf6000000: tme/host/posix/memory rom sun4-75-rev-2.9.bin
zs0 at mainbus0 addr 0xf1000000 ipl 12: tme/machine/sun4/zs
cgthree0 at sbus0 slot 1 offset 0x0 ipl 7: tme/bus/sbus/cgthree
cgthreerom0 at sbus0 slot 1 offset 0x0: tme/host/posix/memory rom
"SUNW,501-1415.bin"
Also CPUs, ROMs and RAMs could be handled to complement the CPU feature system.
next prev parent reply other threads:[~2008-06-21 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 18:12 [Qemu-devel] QEMU configuration files Fabrice Bellard
2008-06-18 19:16 ` [Qemu-devel] " Sebastian Herbszt
2008-06-18 21:08 ` [Qemu-devel] " Anthony Liguori
2008-06-18 23:49 ` Paul Brook
2008-06-19 0:01 ` Paul Brook
2008-06-19 9:46 ` Fabrice Bellard
2008-06-19 11:40 ` Daniel P. Berrange
2008-06-19 11:52 ` Fabrice Bellard
2008-06-19 14:36 ` Daniel P. Berrange
2008-06-19 11:56 ` [Qemu-devel] " Sebastian Herbszt
2008-06-20 13:11 ` Fabrice Bellard
2008-06-21 8:43 ` Blue Swirl [this message]
2008-06-24 15:50 ` [Qemu-devel] " Ian Jackson
2008-06-24 19:50 ` Jamie Lokier
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=f43fc5580806210143v23d5052eydc8ae162798754a@mail.gmail.com \
--to=blauwirbel@gmail.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).