qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <peter.crosthwaite@petalogix.com>,
	qemu-devel@nongnu.org, afaerber@suse.de, agraf@suse.de
Subject: Re: [Qemu-devel] [RFC] Proposal for hw/ split
Date: Mon, 11 Mar 2013 14:12:41 +0100	[thread overview]
Message-ID: <513DD849.2070101@redhat.com> (raw)
In-Reply-To: <CAFEAcA_GKkca1i-vhHggbGGQP8tQE+rNQ9+UY1zmG3gCF+q4cQ@mail.gmail.com>

Il 11/03/2013 14:08, Peter Maydell ha scritto:
>>>> >>> These are little more than SoC containers, aren't they?
>>> >>
>>> >> They're container devices, yes. But why should container devices
>>> >> go under hw/$ARCH ?
>> >
>> > Because they don't really implement any logic, ideally a board should be
>> > a little more than a bunch of container devices.
> This is an argument for putting boards in the same place as
> container devices (which I would agree with), not for putting
> container devices in the same place we currently put boards
> (which I would disagree with).

True.  Still, hw/ARCH is a pretty decent place for boards (and in fact
it was part of "part 1" because it was more or less agreed-upon).

Paolo

  reply	other threads:[~2013-03-11 13:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 11:17 [Qemu-devel] [RFC] Proposal for hw/ split Paolo Bonzini
2013-03-11 11:31 ` Peter Maydell
2013-03-11 11:54   ` Paolo Bonzini
2013-03-11 12:39     ` Peter Maydell
2013-03-11 12:44       ` Paolo Bonzini
2013-03-11 13:08         ` Peter Maydell
2013-03-11 13:12           ` Paolo Bonzini [this message]
2013-03-11 13:19       ` Markus Armbruster
2013-03-11 11:52 ` Edgar E. Iglesias
2013-03-11 13:37 ` Stefan Hajnoczi
2013-03-12  6:48 ` Richard Henderson
2013-03-12  7:33   ` Paolo Bonzini

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=513DD849.2070101@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=peter.crosthwaite@petalogix.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 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).