From: Peter Maydell <peter.maydell@linaro.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] make: automatically include dependencies in recursive subdir rules (v2)
Date: Mon, 18 Jun 2012 11:56:18 +0100 [thread overview]
Message-ID: <CAFEAcA8_puaB6=2FuwfaYr4HNJ2MdMiVfR5VmPUgivpQ5BL4uA@mail.gmail.com> (raw)
In-Reply-To: <4FDF05FC.1060107@suse.de>
On 18 June 2012 11:42, Andreas Färber <afaerber@suse.de> wrote:
> Am 18.06.2012 11:31, schrieb Peter Maydell:
>> (Does architecture-specific separation make much sense in general?
>> Not all devices are architecture-specific. I'd have thought that
>> a functional split eg timer/serial/usb like the linux kernel layout
>> would be better.)
>
> Maybe you're misreading me? I was saying iff a device is specifically
> (not accidentally) for one target foo then it may/should be placed into
> hw/foo/ directory.
Yes, I'm saying that seems like a confusing split, because a few
devices for target foo will be in hw/foo and a number more in hw/,
and there'll probably be cases where something in hw/foo has to
move out into hw/ when a new target comes along that happens to
reuse it. So rather than having hw/foo where foo == target-name,
I'm suggesting hw/foo where foo == kind-of-device. As you say
we've already moved a bit down this road with usb, for instance.
-- PMM
next prev parent reply other threads:[~2012-06-18 10:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 0:01 [Qemu-devel] [PATCH] make: automatically include dependencies in recursive subdir rules (v2) Anthony Liguori
2012-06-18 0:32 ` Andreas Färber
2012-06-18 9:13 ` Jan Kiszka
2012-06-18 9:31 ` Peter Maydell
2012-06-18 10:42 ` Andreas Färber
2012-06-18 10:56 ` Peter Maydell [this message]
2012-06-18 11:35 ` Andreas Färber
2012-06-18 11:45 ` Peter Maydell
2012-06-18 12:47 ` Anthony Liguori
2012-06-18 13:08 ` Jan Kiszka
2012-06-20 13:06 ` Anthony Liguori
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='CAFEAcA8_puaB6=2FuwfaYr4HNJ2MdMiVfR5VmPUgivpQ5BL4uA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=pbonzini@redhat.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).