From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, Paul Sokolovsky <pmiscml@gmail.com>
Cc: andrzej zaborowski <balrog@zabor.org>
Subject: Re: [Qemu-devel] State of TI OMAP board support?
Date: Thu, 3 Aug 2006 04:01:17 +0100 [thread overview]
Message-ID: <200608030401.18161.paul@codesourcery.com> (raw)
In-Reply-To: <958928716.20060803052442@gmail.com>
> > I don't think it is considered for inclusion. Before it is merged I
> > would like to separate the generic OMAP code from board-related code
> > (the board I emulate is the Palm Tunsgten|E handheld), but I imagine
> > the QEMU maintainers won't like the way code is formatted and probably
> > many other things, hard to say.
>
> I really hoped to get response from QEMU author/ARM emulation maintainer
> regarding these points. Paul, any comments? Would you be interested to
> add more CPUs/boards? Any suggestion regarding this? Maybe if it is
> expected that there may be many implementation and they won't fit into
> core distribution, to provide API for plugin development?
I've no objection to adding new boards/cpus[1].
However, unless I have some personal/commercial interest in that particular
board it's up to the patch author(s) to get that support into a state where
I'm happy merging it. If the original author thinks it needs cleanup before
submission I'm inclined to believe them ;-)
All the normal guidelines for patch submission apply. i.e. follow coding
conventions, split changes into logically separate patches, don't mix
cleanups with new features, etc.
Paul
[1] As discussed previously on this list there are unresolved legal issues
with emulating ARMv6/v7 cpus, however that's not relevant in this case.
next prev parent reply other threads:[~2006-08-03 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 8:26 [Qemu-devel] State of TI OMAP board support? Paul Sokolovsky
2006-07-30 13:29 ` andrzej zaborowski
2006-08-03 2:24 ` Re[2]: " Paul Sokolovsky
2006-08-03 3:01 ` Paul Brook [this message]
2006-08-03 3:59 ` andrzej zaborowski
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=200608030401.18161.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=balrog@zabor.org \
--cc=pmiscml@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).