On 5 December 2013 00:20, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
Is hivecs-on-reset ideally a new ARM_FEATURE or is there a simpler
conditional we can use as post_init time?
I think we want the property if (!arm_feature(ARM_FEATURE_M)).
-- PMM
On 5 December 2013 00:25, Peter Crosthwaite
peter.crosthwa...@xilinx.com wrote:
But the bootloader does this already. We have support for board
configurable secondary bootloops. Is this as simple as supporting
board configurable primary boot fragments?
arm_boot needs to be patched to do its
On Thu, 17 Oct 2013 20:17:15 +0100
Peter Maydell peter.mayd...@linaro.org wrote:
On 17 October 2013 19:51, Georg Hofstetter q...@g3gg0.de wrote:
flash (ROM1) on these cameras starts at 0xF800 and is either
0x0080, 0x0100 ox 0x0200 large. just like with every
chip-selected
On 4 December 2013 20:22, Antony Pavlov antonynpav...@gmail.com wrote:
Here is my proposition:
1. qemu board code setup CPU to start from 0x. (0x is a ROM
address
on DIGIC chips)
Sort of. What we need is:
1a. Add a hivecs property to the ARM CPU object (which
just sets
On Wed, 4 Dec 2013 20:29:05 +
Peter Maydell peter.mayd...@linaro.org wrote:
On 4 December 2013 20:22, Antony Pavlov antonynpav...@gmail.com wrote:
Here is my proposition:
1. qemu board code setup CPU to start from 0x. (0x is a ROM
address
on DIGIC chips)
Sort
On 4 December 2013 21:20, Antony Pavlov antonynpav...@gmail.com wrote:
On Wed, 4 Dec 2013 20:29:05 +
Peter Maydell peter.mayd...@linaro.org wrote:
On 4 December 2013 20:22, Antony Pavlov antonynpav...@gmail.com wrote:
Here is my proposition:
1. qemu board code setup CPU to start from
On Thu, Dec 5, 2013 at 7:34 AM, Peter Maydell peter.mayd...@linaro.org wrote:
On 4 December 2013 21:20, Antony Pavlov antonynpav...@gmail.com wrote:
On Wed, 4 Dec 2013 20:29:05 +
Peter Maydell peter.mayd...@linaro.org wrote:
On 4 December 2013 20:22, Antony Pavlov antonynpav...@gmail.com
On Thu, Dec 5, 2013 at 7:20 AM, Antony Pavlov antonynpav...@gmail.com wrote:
On Wed, 4 Dec 2013 20:29:05 +
Peter Maydell peter.mayd...@linaro.org wrote:
On 4 December 2013 20:22, Antony Pavlov antonynpav...@gmail.com wrote:
Here is my proposition:
1. qemu board code setup CPU to
On Thu, 17 Oct 2013 20:17:15 +0100
Peter Maydell peter.mayd...@linaro.org wrote:
On 17 October 2013 19:51, Georg Hofstetter q...@g3gg0.de wrote:
flash (ROM1) on these cameras starts at 0xF800 and is either
0x0080, 0x0100 ox 0x0200 large. just like with every
chip-selected
Am 17.10.2013 21:17, schrieb Peter Maydell:
- make sure the flash emulation supports reflashing (properties)
- change qemu memory subsystem to support execution from a flash that
can be reprogrammed (properties are rewritten during startup)
(maybe this is already possible, but it
On 7 September 2013 08:04, Antony Pavlov antonynpav...@gmail.com wrote:
+
+static void digic4_board_init(DigicBoard *board)
+{
+Error *err = NULL;
+
+DigicBoardState *s = g_new(DigicBoardState, 1);
+
+s-digic = DIGIC(object_new(TYPE_DIGIC));
+
Hello,
just for the record.
flash (ROM1) on these cameras starts at 0xF800 and is either
0x0080, 0x0100 ox 0x0200 large. just like with every
chip-selected memory, where the CS/EN line is selected by address masks,
addressing beyond the size memory repeats the content over and
On 17 October 2013 19:51, Georg Hofstetter q...@g3gg0.de wrote:
flash (ROM1) on these cameras starts at 0xF800 and is either
0x0080, 0x0100 ox 0x0200 large. just like with every
chip-selected memory, where the CS/EN line is selected by address masks,
addressing beyond the size
Also this patch adds initial support for Canon
PowerShot A1100 IS compact camera.
Signed-off-by: Antony Pavlov antonynpav...@gmail.com
---
hw/arm/Makefile.objs | 1 +
hw/arm/digic_boards.c | 88 +++
2 files changed, 89 insertions(+)
create mode
14 matches
Mail list logo
