From: comicinker <comicinker@gmx.de>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] New machine?
Date: Fri, 04 Feb 2011 01:31:05 +0100 [thread overview]
Message-ID: <1296779465.13060.10.camel@arpa> (raw)
In-Reply-To: <AANLkTim=2cpDvaeQnGx2EBtq+cHJgKM0Q=bRjg6U_Gao@mail.gmail.com>
Am Sonntag, den 30.01.2011, 11:13 +0000 schrieb Peter Maydell:
...
>
> > Do I have to patch qemu to support a new machine?
>
> Yes, you would have to implement support for this board,
> and also implement models of any devices which qemu
> doesn't already have (probably most of them). In particular
> if you are interested in a working model of the graphics
> chipset then this is a very large amount of work and might
> even be impossible if the chipset vendor doesn't release
> enough documentation on it. As a rough guide, the code
> to implement (most of) the OMAP3 chipset support in
> qemu is about 29,000 lines of code.
>
> Sorry I don't have a more encouraging answer.
>
> -- PMM
Thank you for your answer. At least I know I can stop searching, which
satisfies me for now. I will get the hardware to go on working.
Regards
C
prev parent reply other threads:[~2011-02-04 0:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 17:00 [Qemu-devel] New machine? Comicinker
2011-01-30 11:13 ` Peter Maydell
2011-02-04 0:31 ` comicinker [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=1296779465.13060.10.camel@arpa \
--to=comicinker@gmx.de \
--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 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).