All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Guang <lig.fnst@cn.fujitsu.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Peter Crosthwaite" <peter.crosthwaite@xilinx.com>,
	"Hervé Poussineau" <hpoussin@reactos.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"Bamvor Jian Zhang" <BJZhang@suse.com>
Subject: Re: [Qemu-devel] [PATCH v4 3/4] hw/arm: add sunxi machine type
Date: Fri, 29 Nov 2013 16:56:13 +0800	[thread overview]
Message-ID: <529856AD.20105@cn.fujitsu.com> (raw)
In-Reply-To: <CAFEAcA8aGSWkYuZOSrw18qif_5Xs7HokmC23xU-B_gQoA743Sg@mail.gmail.com>

Peter Maydell wrote:
> On 29 November 2013 08:06, Li Guang<lig.fnst@cn.fujitsu.com>  wrote:
>    
>> what I design is:
>> we have a sunxi series as a machine, then
>> for sunx4i, we specify -M sunxi -cpu cortex-a8 -device x1 ...
>> for sunx5i, we specify -M sunxi -cpu cortex-a8 -device x2 ...
>> for sunx7i, we specify -M sunxi -cpu cortex-a7 -devcie x3 ...
>> for cubieboard, we specify -M sunxi -cpu -cortex-a8 -device x1 -device p1
>>      
> No, QEMU doesn't work this way. "-M whatever" specifies a board
> model, so in this example it should be "-M cubieboard" and so on.
> That then gives you a particular CPU and set of devices. Obviously
> where we have several board models that share a single SoC they
> share implementation (by instantiating the same SoC object).
> If we have several SoCs that share common subcomponents like
> a UART, then they share implementation by having all those SoCs
> instantiate the same UART object.
>
> -cpu is really only intended where you have a situation like the
> PC where just the CPU can be plugged and unplugged into a
> board; it doesn't fit for SoC-based systems.
> Similarly, -device is really (currently) for pluggable devices like
> ISA or PCI cards -- where the device is a non-removable
> part of the SoC it doesn't work.
>    

why not just say this SoC is a board?
and other board like cubieboard are only
this SoC + several devices,
I think is reasonable, at least in this case.

A10 and A13 both have a cortex-a8, different in HDMI and SATA,
suppose we modeled A10, A10State,
if we add cubieboard, we realize A10,
then we have a board called demoboard based on A13,
what we will do here?
also realize A10?  unlucky, we miss HDMI and SATA difference,
model A13? new a A13State?
but we have most devices the same for A10 & A13.


> As Andreas says, we need to model real actual hardware,
> not some abstraction that kind of matches the kernel's
> abstractions.
>    

I never aimed to do what you said abstraction,
I just specified a represented of real hardware.

> Is "sunxi" what the hardware is actually called, or only
> what the kernel port has been called? More information
> about where this name comes from might make it easier
> to tell if it is the correct one for the QEMU SoC models.
>
>
>    

I tried to contact Allwinner's engineer,
no response until now.

Thanks!
Li Guang

  parent reply	other threads:[~2013-11-29  8:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  7:22 [Qemu-devel] [PATCH v4 0/4] add sunxi machine type liguang
2013-11-26  7:22 ` [Qemu-devel] [PATCH v4 1/4] hw/timer: add sunxi timer device liguang
2013-11-26  8:40   ` Peter Crosthwaite
2013-11-26  8:59     ` Li Guang
2013-11-26  9:14       ` Peter Crosthwaite
2013-11-26  9:19         ` Li Guang
2013-11-26  9:25           ` Peter Crosthwaite
2013-11-26  7:22 ` [Qemu-devel] [PATCH v4 2/4] hw/intc: add sunxi interrupt controller device liguang
2013-11-26  9:02   ` Peter Crosthwaite
2013-11-26  9:11     ` Li Guang
2013-11-27  3:36       ` Li Guang
2013-11-27  5:31         ` Peter Crosthwaite
2013-11-27  5:44           ` Li Guang
2013-11-26  7:22 ` [Qemu-devel] [PATCH v4 3/4] hw/arm: add sunxi machine type liguang
2013-11-26  9:22   ` Peter Crosthwaite
2013-11-27  0:22     ` Li Guang
2013-11-27  9:22     ` Andreas Färber
2013-11-27  9:27       ` Andreas Färber
2013-11-29  0:46         ` Li Guang
2013-11-29  0:53           ` Peter Crosthwaite
2013-11-29  3:27           ` Andreas Färber
2013-11-29  8:06             ` Li Guang
2013-11-29  8:31               ` Peter Maydell
2013-11-29  8:49                 ` Bamvor Jian Zhang
2013-11-29 13:51                   ` Andreas Färber
2013-11-29  8:56                 ` Li Guang [this message]
2013-11-29  9:11                   ` Peter Maydell
2013-11-29  8:41               ` Bamvor Jian Zhang
2013-11-29  9:01                 ` Li Guang
2013-11-29 13:04               ` Andreas Färber
2013-12-01 11:48                 ` Peter Crosthwaite
2013-12-02  4:30                 ` Li Guang
2013-11-26  7:22 ` [Qemu-devel] [PATCH v4 4/4] MAINTAINERS: add myself to maintain sunxi machine liguang

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=529856AD.20105@cn.fujitsu.com \
    --to=lig.fnst@cn.fujitsu.com \
    --cc=BJZhang@suse.com \
    --cc=afaerber@suse.de \
    --cc=hpoussin@reactos.org \
    --cc=peter.crosthwaite@xilinx.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.