qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Li Guang <lig.fnst@cn.fujitsu.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Andreas Färber" <afaerber@suse.de>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 3/4] hw/arm: add sunxi machine type
Date: Wed, 27 Nov 2013 08:22:24 +0800	[thread overview]
Message-ID: <52953B40.1050406@cn.fujitsu.com> (raw)
In-Reply-To: <CAEgOgz4MZuF_dXnYiQ3DynxA9cDJRVLkLuamZB+cV4Q9etFwNw@mail.gmail.com>

Peter Crosthwaite wrote:
> On Tue, Nov 26, 2013 at 5:22 PM, liguang<lig.fnst@cn.fujitsu.com>  wrote:
>    
>> Signed-off-by: liguang<lig.fnst@cn.fujitsu.com>
>> ---
>>   hw/arm/Makefile.objs |    1 +
>>   hw/arm/sunxi-soc.c   |   98 ++++++++++++++++++++++++++++++++++++++++++++++++++
>>   2 files changed, 99 insertions(+), 0 deletions(-)
>>   create mode 100644 hw/arm/sunxi-soc.c
>>
>> diff --git a/hw/arm/Makefile.objs b/hw/arm/Makefile.objs
>> index 3671b42..f9f3071 100644
>> --- a/hw/arm/Makefile.objs
>> +++ b/hw/arm/Makefile.objs
>> @@ -5,3 +5,4 @@ obj-y += tosa.o versatilepb.o vexpress.o xilinx_zynq.o z2.o
>>
>>   obj-y += armv7m.o exynos4210.o pxa2xx.o pxa2xx_gpio.o pxa2xx_pic.o
>>   obj-y += omap1.o omap2.o strongarm.o
>> +obj-y += sunxi-soc.o
>> diff --git a/hw/arm/sunxi-soc.c b/hw/arm/sunxi-soc.c
>> new file mode 100644
>> index 0000000..b45af6d
>> --- /dev/null
>> +++ b/hw/arm/sunxi-soc.c
>> @@ -0,0 +1,98 @@
>> +/*
>> + * Allwinner sunxi series SoC emulation
>> + *
>> + * Copyright (C) 2013 Li Guang
>> + * Written by Li Guang<lig.fnst@cn.fujitsu.com>
>> + *
>> + * This program is free software; you can redistribute it and/or modify it
>> + * under the terms of the GNU General Public License as published by the
>> + * Free Software Foundation; either version 2 of the License, or
>> + * (at your option) any later version.
>> + *
>> + * This program is distributed in the hope that it will be useful, but WITHOUT
>> + * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
>> + * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
>> + * for more details.
>> + */
>> +
>> +#include "hw/sysbus.h"
>> +#include "hw/devices.h"
>> +#include "hw/boards.h"
>> +#include "hw/arm/arm.h"
>> +#include "hw/ptimer.h"
>> +#include "hw/char/serial.h"
>> +#include "hw/timer/sunxi-pit.h"
>> +#include "hw/intc/sunxi-pic.h"
>> +
>> +#include "sysemu/sysemu.h"
>> +#include "exec/address-spaces.h"
>> +
>> +
>> +#define SUNXI_PIC_REG_BASE 0x01c20400
>> +#define SUNXI_PIT_REG_BASE 0x01c20c00
>> +#define SUNXI_UART0_REG_BASE 0x01c28000
>> +
>> +static struct arm_boot_info sunxi_binfo = {
>> +    .loader_start = 0x40000000,
>> +    .board_id = 0x1008,
>> +};
>> +
>> +static void sunxi_init(QEMUMachineInitArgs *args)
>>      
> I would check with Andreas/PMM on what the go is with SoCs regarding
> container devices and boards. My (vague) understanding is that SoCs
> should be container devices and boards instantiate those containers
> with off-chip connectivity. This seems flat to me, with everything on
> board level.
>
>    
well, interesting thought.

IMO, SoC is a board.

>> +{
>> +    ram_addr_t ram_size = args->ram_size;
>> +    const char *cpu_model = args->cpu_model;
>> +    const char *kernel_filename = args->kernel_filename;
>> +    const char *kernel_cmdline = args->kernel_cmdline;
>> +    ARMCPU *cpu;
>> +    MemoryRegion *address_space_mem = get_system_memory();
>> +    MemoryRegion *ram = g_new(MemoryRegion, 1);
>> +    MemoryRegion *ram_alias = g_new(MemoryRegion, 1);
>> +    qemu_irq pic[95];
>>      
> [SUNXI_PIC_INT_NR]
>
>
>    
yes, will fix.

Thanks!
Li Guang
>    
>> +    DeviceState *dev;
>> +    uint8_t i;
>> +
>> +    /*here we currently support sunxi-4i*/
>> +    cpu_model = "cortex-a8";
>> +    cpu = cpu_arm_init(cpu_model);
>> +    if (!cpu) {
>> +        fprintf(stderr, "Unable to find CPU definition\n");
>> +        exit(1);
>> +    }
>> +
>> +    memory_region_init_ram(ram, NULL, "sunxi-soc.ram", ram_size);
>> +    memory_region_add_subregion(address_space_mem, 0, ram);
>> +    memory_region_init_alias(ram_alias, NULL, "ram.alias", ram, 0, ram_size);
>> +    memory_region_add_subregion(address_space_mem, 0x40000000, ram_alias);
>> +
>> +    dev = sysbus_create_varargs(TYPE_SUNXI_PIC, SUNXI_PIC_REG_BASE,
>> +                                qdev_get_gpio_in(DEVICE(cpu), ARM_CPU_IRQ),
>> +                                qdev_get_gpio_in(DEVICE(cpu), ARM_CPU_FIQ),
>> +                                NULL);
>> +    for (i = 0; i<  SUNXI_PIC_INT_NR; i++) {
>> +        pic[i] = qdev_get_gpio_in(dev, i);
>> +    }
>> +
>> +    sysbus_create_varargs(TYPE_SUNXI_PIT, SUNXI_PIT_REG_BASE, pic[22], pic[23],
>> +                          pic[24], pic[25], pic[67], pic[68], NULL);
>> +
>> +    serial_mm_init(address_space_mem, SUNXI_UART0_REG_BASE, 2, pic[1], 115200,
>> +                    serial_hds[0], DEVICE_NATIVE_ENDIAN);
>> +
>> +    sunxi_binfo.ram_size = ram_size;
>> +    sunxi_binfo.kernel_filename = kernel_filename;
>> +    sunxi_binfo.kernel_cmdline = kernel_cmdline;
>> +    arm_load_kernel(cpu,&sunxi_binfo);
>> +}
>> +
>> +static QEMUMachine sunxi_machine = {
>> +    .name = "sunxi",
>> +    .desc = "Allwinner's SoC (sunxi series)",
>> +    .init = sunxi_init,
>> +};
>> +
>> +static void sunxi_machine_init(void)
>> +{
>> +    qemu_register_machine(&sunxi_machine);
>> +}
>> +
>> +machine_init(sunxi_machine_init);
>> --
>> 1.7.2.5
>>
>>
>>      
>    

  reply	other threads:[~2013-11-27  0:24 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 [this message]
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
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=52953B40.1050406@cn.fujitsu.com \
    --to=lig.fnst@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --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 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).