On Wed, 2016-11-23 at 09:48 +0100, Cédric Le Goater wrote:
> On 11/23/2016 01:46 AM, Alastair D'Silva wrote:
> > On Tue, 2016-11-22 at 17:56 +0100, Cédric Le Goater wrote:
> > > On 11/17/2016 05:36 AM, Alastair D'Silva wrote:
> > > >
> > > > > > > > From: Alastair D'Silva
>
On Mon, 2016-11-14 at 08:14 +0100, Cédric Le Goater wrote:
> > Given the starting point of the tmp105 code the patch looks okay, but I
> > was a bit thrown by the use of the 'len' member as what I'd consider an
> > index. For instance we reset len to zero in tmp421_event() after
> > populating
es a certain number of checks before doing
> so.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/ssi/aspeed_smc.c | 135
> ++--
> 1 file changed, 130 inser
e controller.
>
> Also rewrite a bit the comments in the code on this topic.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/ssi/aspeed_smc.c | 16 +---
> 1 file changed, 13 insertion
BMC SPI controller and add a new
> SPI controller for the host. We also have to introduce new type names
> to handle the differences in the flash modules memory mappping.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and..
On Tue, 2016-09-27 at 13:57 +0200, Cédric Le Goater wrote:
> The AST2500 SoC has two. Let's prepare ground for the next changes
> which will add the required definitions for the second host SPI
> controller.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Review
ic Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/aspeed_soc.c | 9 -
> hw/ssi/aspeed_smc.c | 15 +++
> include/hw/ssi/aspeed_smc.h | 3 ++-
> 3 files changed, 17 insertions(+), 10 deletions(
AST2500 SoC and the SMC, which was still available
> on the AST2400 SoC, was removed.
>
> The Aspeed SoC does not provide support for the legacy SMC
> controller. So, let's rename the 'smc' object to 'fmc' to clarify its
> nature.
>
> Signed-off-by: Cédric Le Goater <c...@ka
On Fri, 2016-09-09 at 18:22 +0200, Cédric Le Goater wrote:
> If the RAM size is invalid, the memory controller will use a default
> value.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/aspeed.c | 1
On Fri, 2016-09-09 at 18:22 +0200, Cédric Le Goater wrote:
> Configure the size of the RAM of the SOC using a property to propagate
> the value down to the memory controller from the board level.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffer
On Fri, 2016-09-09 at 18:22 +0200, Cédric Le Goater wrote:
> Also change the default value used in case of an error. The minimum
> size is a bit severe, so let's just use an average RAM size.
I'm not sure we should be switching the default value in this patch,
but I'm not sure it's worth any
On Fri, 2016-09-09 at 18:22 +0200, Cédric Le Goater wrote:
> There is no need to do this at each reset as the RAM size will not
> change.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/m
On Tue, 2016-08-02 at 19:15 +0200, Cédric Le Goater wrote:
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/aspeed.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/hw/arm/aspeed.c b/hw/arm
On Tue, 2016-08-02 at 19:15 +0200, Cédric Le Goater wrote:
> The ast2500 eval board has a hardware strapping register value of
> 0xF100C2E6 which we use for a definition of AST2500_EVB_HW_STRAP1
> below.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Review
On Tue, 2016-08-02 at 19:15 +0200, Cédric Le Goater wrote:
> Based on previous work done by Andrew Jeffery <and...@aj.id.au>.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
>
> Changes since
On Tue, 2016-08-02 at 19:15 +0200, Cédric Le Goater wrote:
> This gives some explanation behind the magic number 0x120CE416.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
>
> Changes since v2:
>
>
On Tue, 2016-08-02 at 19:15 +0200, Cédric Le Goater wrote:
> aspeed_board_init() now uses a board identifier to customize some values
> specific to the board.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
>
ic Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/aspeed.c | 56 +---
> 1 file changed, 37 insertions(+), 19 deletions(-)
>
> diff --git a/hw/arm/aspeed.c b/hw/arm/aspeed.c
On Tue, 2016-08-02 at 19:15 +0200, Cédric Le Goater wrote:
> We plan to add more Aspeed boards to this file. There are no changes
> in the code.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/Mak
-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/aspeed_soc.c | 27 ---
> hw/arm/palmetto-bmc.c | 12
> include/hw/arm/aspeed_soc.h | 17 -
> 3
SoC AST2500, so this provides us a better common base for
> the address space mapping on both SoCs.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
> hw/arm/aspeed_soc.c | 95 ++-
peed_soc.o palmetto-bmc.o
> diff --git a/hw/arm/aspeed_soc.c b/hw/arm/aspeed_soc.c
> new file mode 100644
> index ..b272f4e48cfc
> --- /dev/null
> +++ b/hw/arm/aspeed_soc.c
> @@ -0,0 +1,229 @@
> +/*
> + * AST2400 SoC
> + *
> + * Andrew Jeffery <and...@aj
On Sat, 2016-07-30 at 10:35 +0200, Cédric Le Goater wrote:
> On 07/29/2016 03:16 AM, Andrew Jeffery wrote:
> >
> > On Thu, 2016-07-28 at 09:51 +0200, Cédric Le Goater wrote:
> > >
> > > On 07/28/2016 04:14 AM, Andrew Jeffery wrote:
> > > >
>
On Thu, 2016-07-28 at 09:51 +0200, Cédric Le Goater wrote:
> On 07/28/2016 04:14 AM, Andrew Jeffery wrote:
> >
> > On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> > >
> > > The SCU controler holds the board revision number in its 0x7C
> >
On Thu, 2016-07-28 at 09:15 +0200, Cédric Le Goater wrote:
> >
> > Also, the meaning of the bits have changed from the AST2400 - they
> > probably should be documented somewhere?
>
> So you want me send to an updated version of :
>
>
On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> Signed-off-by: Cédric Le Goater
> ---
> hw/arm/palmetto-bmc.c| 32 +++-
> include/hw/arm/ast2400.h | 5 +
> 2 files changed, 36 insertions(+), 1 deletion(-)
>
> diff --git
On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> This is mostly a name replacement to prepare ground for other socs
> specificities. It also adds a specific TypeInfo struct for the
> palmetto_bmc board with a custom initialization for the same reason.
I think we should rename the
On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> Based on previous work done by Andrew Jeffery <and...@aj.id.au>.
>
> Signed-off-by: Cédric Le Goater <c...@kaod.org>
Reviewed-by: Andrew Jeffery <and...@aj.id.au>
> ---
>
On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> aspeed_init() now uses a board identifier to customize some values
> specific to the board, ram base, board revision number, etc.
>
> Signed-off-by: Cédric Le Goater
Looks okay to me, some minor comments below:
> ---
>
On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> It will be easier to specify a different cpu for other soc derived
> from the ast2400 soc.
>
> Signed-off-by: Cédric Le Goater
> ---
> hw/arm/ast2400.c | 8 +++-
> hw/arm/palmetto-bmc.c | 1 +
> 2 files
On Wed, 2016-07-27 at 18:46 +0200, Cédric Le Goater wrote:
> The SCU controler holds the board revision number in its 0x7C
> register. Let's use an alias to link a "silicon-rev" property of the
> soc to the "silicon-rev" property of the SCU controler.
>
> The SDMC controler "silicon-rev" property
On Mon, 2016-07-04 at 14:18 +0200, Cédric Le Goater wrote:
> The uboot in the previous release of the SDK was using a hardcoded
> value for memory size. This is not true anymore, the value is now
> retrieved from the memory controller.
>
> Below is a model for this device, only supporting unlock
In function
> ‘aspeed_scu_write’:
> /home/travis/build/pranith/qemu/hw/misc/aspeed_scu.c:154:23: error:
> ‘LOG_GUEST_ERROR’ undeclared (first use in this function)
>
> This is caused by a missing header file. Fix it.
>
> Signed-off-by: Pranith Kumar <bobby.pr...@gmail.com&g
On Mon, 2016-06-27 at 14:47 +0100, Peter Maydell wrote:
> On 24 June 2016 at 05:58, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > Hi all,
> >
> > These are three patches implementing minimal functionality for the ASPEED
> > System
> > Control Un
On Mon, 2016-06-27 at 14:42 +0100, Peter Maydell wrote:
> On 24 June 2016 at 05:58, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > The SCU is a collection of chip-level control registers that manage the
> > various functions supported by ASPEED SoCs. Typically the bi
: Configure MAC#2 for RMII/NCSI
* 6: Configure MAC#1 for RMII/NCSI
* 5: No VGA BIOS ROM
* 4: Boot using 32bit SPI address mode
* 3:2: Select 16MB VGA memory
* 1:0: Boot from SPI flash memory
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
Reviewed-by: Cédric Le Goater <c...@kaod.org&
-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v2:
* Fix mixing of offsets and register indexes
* Sanity check device property values
* Move trace event definition to hw/misc/trace-events
Since v1:
* Move reset values into SCU implementation (also make register defines private)
*
By specifying the silicon revision we select the appropriate reset
values for the SoC.
Additionally, expose hardware strapping properties aliasing those
provided by the SCU for board-specific configuration.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
Reviewed-by: Cédric Le Goa
hardware strapping values via properties
Andrew Jeffery (3):
hw/misc: Add a model for the ASPEED System Control Unit
ast2400: Integrate the SCU model and set silicon revision
palmetto-bmc: Configure the SCU's hardware strapping register
hw/arm/ast2400.c | 21
hw/arm/palmetto
On Thu, 2016-06-23 at 18:39 +0100, Peter Maydell wrote:
> On 23 June 2016 at 03:15, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > The magic constant configures the following options:
> >
> > * 28:27: Configure DRAM size as 256MB
> > * 26:24: DDR3 SDRAM w
On Thu, 2016-06-23 at 18:42 +0100, Peter Maydell wrote:
> On 23 June 2016 at 03:15, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > The SCU is a collection of chip-level control registers that manage the
> > various functions supported by ASPEED SoCs. Typically the bi
On Thu, 2016-06-23 at 18:37 +0100, Peter Maydell wrote:
> On 23 June 2016 at 03:15, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > The SCU is a collection of chip-level control registers that manage the
> > various functions supported by ASPEED SoCs. Typically the bi
: Configure MAC#2 for RMII/NCSI
* 6: Configure MAC#1 for RMII/NCSI
* 5: No VGA BIOS ROM
* 4: Boot using 32bit SPI address mode
* 3:2: Select 16MB VGA memory
* 1:0: Boot from SPI flash memory
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
hw/arm/palmetto-bmc.c | 2 ++
1 file chan
By specifying the silicon revision we select the appropriate reset
values for the SoC.
Additionally, expose hardware strapping properties aliasing those
provided by the SCU for board-specific configuration.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v1:
* Remove reset
-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v1:
* Move reset values into SCU implementation (also make register defines private)
* Expose silicon-rev property which is used to select appropriate reset values
* Expose hw-strap1/hw-strap2 properties for board-specific SoC configuratio
, influencing the configuration of the
software and the software's configuration of the SoC.
Since v1:
* Select reset values based on silicon ID
* Expose hardware strapping values via properties
Cheers,
Andrew
Andrew Jeffery (3):
hw/misc: Add a model for the ASPEED System Control Unit
ast2400
On Tue, 2016-06-21 at 07:56 +0100, Peter Maydell wrote:
> On 21 June 2016 at 04:49, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > On Mon, 2016-06-20 at 14:57 +0100, Peter Maydell wrote:
> > >
> > > I think there are a couple of plausible ways you might
On Mon, 2016-06-20 at 14:57 +0100, Peter Maydell wrote:
> On 20 June 2016 at 04:44, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > On Fri, 2016-06-17 at 15:22 +0100, Peter Maydell wrote:
> > >
> > > +static Property aspeed_scu_properties[]
On Fri, 2016-06-17 at 15:22 +0100, Peter Maydell wrote:
On 16 June 2016 at 08:48, Andrew Jeffery <and...@aj.id.au> wrote:
The SCU is a collection of chip-level control registers that manage the
various functions supported by the AST2400. Typically the bits control
interactions with
of the software and the
software's configuration of the SoC.
Cheers,
Andrew
Andrew Jeffery (2):
hw/misc: Add a model for the ASPEED System Control Unit
ast2400: Integrate the SCU model and configure reset values
hw/arm/ast2400.c | 57 +
hw/misc/Makefile.objs
Almost all configured reset values are specified by the datasheet. The
notable exception is ASPEED_SCU_SOC_SCRATCH1, where we mark the DRAM as
successfully initialised by the SoC to avoid unnecessary dark corners in
the SoC's u-boot support.
Signed-off-by: Andrew Jeffery <and...@aj.id
of the state to determine how to boot, but the
reset values vary from SoC to SoC. qdev properties are exposed so that
the integrating SoC model can configure the appropriate reset values.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
Reviewed-by: Cédric Le Goater <c...@kaod.org>
Revie
Value matching allows Linux to boot with CONFIG_NO_HZ_IDLE=y on the
palmetto-bmc machine. Two match registers are provided for each timer.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v1: Address comments from Peter
* Switch calculations to use muldiv64()
* Switch to loop
On Fri, 2016-06-10 at 11:42 +0100, Peter Maydell wrote:
> On 10 June 2016 at 01:59, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > On Thu, 2016-06-09 at 19:15 +0100, Peter Maydell wrote:
> > >
> > > On 27 May 2016 at 06:08, Andrew Jeffery <and...@aj.id.
On Thu, 2016-06-09 at 19:15 +0100, Peter Maydell wrote:
> On 27 May 2016 at 06:08, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > Value matching allows Linux to boot with CONFIG_NO_HZ_IDLE=y on the
> > palmetto-bmc machine. Two match registers are provided for each
On Mon, 2016-06-06 at 15:01 +0100, Peter Maydell wrote:
> On 27 May 2016 at 06:08, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > Value matching allows Linux to boot with CONFIG_NO_HZ_IDLE=y on the
> > palmetto-bmc machine. Two match registers are provided for each
Value matching allows Linux to boot with CONFIG_NO_HZ_IDLE=y on the
palmetto-bmc machine. Two match registers are provided for each timer.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
The change pulls out ptimer in favour of the regular timer infrastructure. As a
consequence it impl
On Mon, 2016-05-23 at 07:55 +0200, Cédric Le Goater wrote:
> >
> > The hunk fails to apply to master as the SCU isn't yet integrated
> > there. The change to ast2400.h also fails to apply for this reason.
>
> Ah yes. I am using your branch for this patch.
>
> So, I will provide you a fix for
Hi Cédric,
On Fri, 2016-05-20 at 18:31 +0200, Cédric Le Goater wrote:
> Largely inspired by the TMP105 temperature sensor, this patch brings
> to Qemu a model for TMP42{1,2,3} temperature sensors.
>
> Specs can be found here :
>
> http://www.ti.com/lit/gpn/tmp421
>
> Signed-off-by:
warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, see .
> + *
> + */
> +
> +#include "qemu/osde
configured with aspeed_defconfig.
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v4:
* Fix to compile when using GCC 4.x
* Drop unnecessary asserts
Since v3:
* Drop unnecessary mention of VMStateDescription in timer_t
), but creating specific machine types is preferable
to a generic machine that doesn't match any particular hardware.
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v4:
* Rename to hw/arm/palmetto-bmc.c, update functions, s
:
Addressed reviews/comments from:
* Cédric Le Goater
Andrew Jeffery (4):
hw/timer: Add ASPEED timer device model
hw/intc: Add (new) ASPEED VIC device model
hw/arm: Add ASPEED AST2400 SoC model
hw/arm: Add palmetto-bmc machine
default-configs/arm-softmmu.mak | 1 +
hw/arm
While the ASPEED AST2400 SoC[1] has a broad range of capabilities this
implementation is minimal, comprising an ARM926 processor, ASPEED VIC
and timer devices, and a 8250 UART.
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Si
will not be serviced (however the access will be logged).
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v3:
* Switch from g_assert() to qemu_log_mask(LOG_GUEST_ERROR, ...) in guest path
Since v2:
* Implement all sup
On Tue, 2016-03-15 at 11:25 +0100, Cédric Le Goater wrote:
> On 03/15/2016 06:01 AM, Andrew Jeffery wrote:
> > On Tue, 2016-03-15 at 12:34 +0800, Jeremy Kerr wrote:
> > > Hi Andrew,
> > >
> > > > This patch series models enough of the ASPEED AST2400 ARM9 SoC
On Tue, 2016-03-15 at 14:14 +0100, Cédric Le Goater wrote:
> On 03/14/2016 05:13 AM, Andrew Jeffery wrote:
> > Implement basic ASPEED timer functionality for the AST2400 SoC[1]: Up to
> > 8 timers can independently be configured, enabled, reset and disabled.
> > S
Hi Dmitry,
On Tue, 2016-03-15 at 21:14 +0300, Dmitry Osipenko wrote:
> Hello Andrew,
>
> 14.03.2016 07:13, Andrew Jeffery пишет:
> > Implement basic ASPEED timer functionality for the AST2400 SoC[1]: Up to
> > 8 timers can independently be configured, enabled, reset a
On Tue, 2016-03-15 at 12:34 +0800, Jeremy Kerr wrote:
> Hi Andrew,
>
> > This patch series models enough of the ASPEED AST2400 ARM9 SoC[0] to
> > boot an aspeed_defconfig Linux kernel[1][2]. Specifically, the series
> > implements the ASPEED timer and VIC devices, integrates them into an
> >
configured with aspeed_defconfig.
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v3:
* Drop unnecessary mention of VMStateDescription in timer_to_ctrl description
* Mention hw/timer/a9gtimer.c with respect to clock value ma
to be a
common, formal name for the hardware configuration that isn't generic
(e.g. 'BMC' or 'AST2400').
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v3:
* Split the machine from the SoC implementation
I've gone the
will not be serviced (however the access will be logged).
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v3:
* Switch from g_assert() to qemu_log_mask(LOG_GUEST_ERROR, ...) in guest path
Since v2:
* Implement all sup
While the ASPEED AST2400 SoC[1] has a broad range of capabilities this
implementation is minimal, comprising an ARM926 processor, ASPEED VIC
and timer devices, and a 8250 UART.
[1] http://www.aspeedtech.com/products.php?fPath=20=376
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Si
* Joel Stanley
Changes since v1:
Addressed reviews/comments from:
* Cédric Le Goater
Andrew Jeffery (4):
hw/timer: Add ASPEED timer device model
hw/intc: Add (new) ASPEED VIC device model
hw/arm: Add an ASPEED AST2400 SoC
hw/arm: Add opbmc2400, an AST2400-based OpenPOWER BMC machine
On Fri, 2016-03-11 at 16:03 +0700, Peter Maydell wrote:
> On 5 March 2016 at 11:29, Andrew Jeffery <and...@aj.id.au> wrote:
> > Implement a basic ASPEED VIC device model, enough to boot a Linux kernel
> > configured with aspeed_defconfig. The model implements the 'new'
>
On Fri, 2016-03-11 at 15:56 +0700, Peter Maydell wrote:
> On 5 March 2016 at 11:29, Andrew Jeffery <and...@aj.id.au> wrote:
> > Implement basic AST2400 timer functionality: Up to 8 timers can
> > independently be configured, enabled, reset and disabled. A couple of
with aspeed_defconfig.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v2:
* Improve handling of timer configuration with respect to enabled state
* Remove redundant enabled member from AspeedTimer
* Implement VMStateDescriptions
* Fix interrupt behaviour (edge triggered, both
the access will be logged).
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v2:
* Implement all supported interrupt types and configurations
* Implement a VMStateDescription
* Log accesses to legacy IO space
* Add documentation on some implementation and hardware details
*
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
Since v2:
* Implement a SOC model to move code out from the machine definition
* Rework the machine to better use QOM
* Include qemu/osdep.h
* Revert back to qemu_log_mask(LOG_UNIMP, ...) in IO handlers
Since v1:
hw/arm/Makefile.objs
Maydell
* Alexey Kardashevskiy
* Joel Stanley
Changes since v1:
Addressed reviews/comments from:
* Cédric Le Goater
Andrew Jeffery (3):
hw/timer: Add ASPEED timer device model
hw/intc: Add (new) ASPEED VIC device model
hw/arm: Add ASPEED AST2400 machine model
default-configs/arm
On Thu, 2016-03-03 at 08:39 +, Peter Maydell wrote:
> On 3 March 2016 at 05:14, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > On Thu, 2016-02-25 at 16:29 +, Peter Maydell wrote:
> > >
> > > >
> > > > +case 0x20: /* Inte
On Thu, 2016-02-25 at 16:29 +, Peter Maydell wrote:
> > +case 0x20: /* Interrupt Enable */
> > +s->int_enable |= data;
>
> Are you sure this only ORs in new 1 bits?
As in, am I sure I only want to take the newly set bits? If so, yes, as
the the following register serves to clear
Hi Peter,
On Thu, 2016-02-25 at 16:29 +, Peter Maydell wrote:
> On 16 February 2016 at 11:34, Andrew Jeffery <and...@aj.id.au> wrote:
> > Implement a minimal ASPEED AVIC device model, enough to boot a Linux
> > kernel configured with aspeed_defconfig. The VI
On Fri, 2016-02-26 at 10:20 +, Peter Maydell wrote:
> On 26 February 2016 at 03:14, Andrew Jeffery <and...@aj.id.au> wrote:
> >
> > Hi Peter,
> >
> > On Thu, 2016-02-25 at 16:11 +, Peter Maydell wrote:
> > >
> > > On 16 February 20
Hi Peter,
On Thu, 2016-02-25 at 16:11 +, Peter Maydell wrote:
> On 16 February 2016 at 11:34, Andrew Jeffery <and...@aj.id.au> wrote:
> > Implement basic AST2400 timer functionality: Timers can be configured,
> > enabled, reset and disabled.
> >
> &
the provided offset to understand
whether the access is requesting the lower or upper 32bits of the 64bit
quantity.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
hw/intc/Makefile.objs| 1 +
hw/intc/aspeed_vic.c | 256 +++
include/h
with
aspeed_defconfig.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
default-configs/arm-softmmu.mak | 2 +
hw/timer/Makefile.objs | 2 +
hw/timer/aspeed_timer.c | 313
include/hw/timer/aspeed_timer.h | 55 +++
trace-
:
* Refactor initialisation of and respect requested clock rates (APB/External)
* Simplify some index calculations
===
Andrew Jeffery (3):
hw/timer: Add ASPEED AST2400 timer device model
hw/intc: Add (new) ASPEED AST2400 AVIC device model
hw/arm: Add ASPEED AST2400 machine type
default
Adds the AST2400 machine type with ASPEED AVIC and timer models. The
new machine type is functional enough to boot Linux to userspace.
Signed-off-by: Andrew Jeffery <and...@aj.id.au>
---
hw/arm/Makefile.objs | 1 +
hw/arm/ast2400.c
201 - 289 of 289 matches
Mail list logo