From: Stefan Weil <sw@weilnetz.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"James Hogan" <james.hogan@imgtec.com>,
"Peter Jovanovic" <petar.jovanovic@imgtec.com>,
qemu-devel@nongnu.org, "Hervé Poussineau" <hpoussin@reactos.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] Free BIOS for MIPS Malta (was: mips_malta: do not raise exceptions when accessing invalid memory)
Date: Wed, 14 Aug 2013 07:18:22 +0200 [thread overview]
Message-ID: <520B131E.6050808@weilnetz.de> (raw)
In-Reply-To: <20130813212631.GJ22508@hall.aurel32.net>
Am 13.08.2013 23:26, schrieb Aurelien Jarno:
> On Tue, Aug 13, 2013 at 10:20:41PM +0100, Peter Maydell wrote:
>> On 13 August 2013 22:15, Aurelien Jarno <aurelien@aurel32.net> wrote:
>>> I agree that Andreas is taking time to update the various devices,
>>> thanks. That said he's not the one who has introduced this new API, and
>>> that should not be a justification for removing the Malta board or even
>>> the MIPS target from QEMU.
>> Has anybody suggested that? I don't think we're anywhere near
>> that stage yet (and I'd certainly object at this point to
>> dropping devices simply because they hadn't been QOMified).
> We have seen some patches in the past intentionally breaking
> non-qdevified devices, and it has been suggested on IRC to schedule
> MIPS target for removal because there was no free bios available.
Redboot / eCOS is free and available in source for Malta:
http://ecos.sourceware.org/docs-latest/redboot/malta.html
Some years ago I testedit with QEMU and was able to build
(there are no pre-built binaries for Malta) and run it (command
prompt, basic commands).
There are also some recent mails on using U-Boot with MIPS Malta:
http://lists.denx.de/pipermail/u-boot/2013-January/144505.html
So we have at least two free BIOS available.
The large number of systems, devices and file systemswhich are
supported is one of the really great features of QEMU.I don't
want to miss this diversity, although I am aware that commercial
distributors are more interested in features which support their
business like KVM, configuration or migration.
Regards,
Stefan
prev parent reply other threads:[~2013-08-14 5:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 19:44 [Qemu-devel] [PATCH for-1.6] mips_malta: do not raise exceptions when accessing invalid memory Aurelien Jarno
2013-08-12 20:38 ` Stefan Weil
2013-08-12 21:18 ` Aurelien Jarno
2013-08-13 10:05 ` James Hogan
2013-08-13 12:32 ` Andreas Färber
2013-08-13 20:23 ` Aurelien Jarno
2013-08-13 20:45 ` Peter Maydell
2013-08-13 21:15 ` Aurelien Jarno
2013-08-13 21:20 ` Peter Maydell
2013-08-13 21:26 ` Aurelien Jarno
2013-08-14 5:18 ` Stefan Weil [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=520B131E.6050808@weilnetz.de \
--to=sw@weilnetz.de \
--cc=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=hpoussin@reactos.org \
--cc=james.hogan@imgtec.com \
--cc=petar.jovanovic@imgtec.com \
--cc=peter.maydell@linaro.org \
--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 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.