On 5 December 2013 00:25, Peter Crosthwaite
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 bootstrap magic with no -
On 5 December 2013 00:20, Peter Crosthwaite
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 Thu, Dec 5, 2013 at 7:20 AM, Antony Pavlov wrote:
> On Wed, 4 Dec 2013 20:29:05 +
> Peter Maydell wrote:
>
>> On 4 December 2013 20:22, Antony Pavlov wrote:
>> > Here is my proposition:
>> >
>> > 1. qemu board code setup CPU to start from 0x. (0x is a
>> > ROM address
>>
On Thu, Dec 5, 2013 at 7:34 AM, Peter Maydell wrote:
> On 4 December 2013 21:20, Antony Pavlov wrote:
>> On Wed, 4 Dec 2013 20:29:05 +
>> Peter Maydell wrote:
>>
>>> On 4 December 2013 20:22, Antony Pavlov wrote:
>>> > Here is my proposition:
>>> >
>>> > 1. qemu board code setup CPU to star
On 4 December 2013 21:20, Antony Pavlov wrote:
> On Wed, 4 Dec 2013 20:29:05 +
> Peter Maydell wrote:
>
>> On 4 December 2013 20:22, Antony Pavlov wrote:
>> > Here is my proposition:
>> >
>> > 1. qemu board code setup CPU to start from 0x. (0x is a
>> > ROM address
>> > on D
On Wed, 4 Dec 2013 20:29:05 +
Peter Maydell wrote:
> On 4 December 2013 20:22, Antony Pavlov 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 "hi
On 4 December 2013 20:22, Antony Pavlov 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 env->cp15.c1_sys bit
On Thu, 17 Oct 2013 20:17:15 +0100
Peter Maydell wrote:
> On 17 October 2013 19:51, Georg Hofstetter 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
On Thu, 17 Oct 2013 20:17:15 +0100
Peter Maydell wrote:
> On 17 October 2013 19:51, Georg Hofstetter 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
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, bu
On 17 October 2013 19:51, Georg Hofstetter 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 memory rep
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 ove
On 7 September 2013 08:04, Antony Pavlov wrote:
> +
> +static void digic4_board_init(DigicBoard *board)
> +{
> +Error *err = NULL;
> +
> +DigicBoardState *s = g_new(DigicBoardState, 1);
> +
> +s->digic = DIGIC(object_new(TYPE_DIGIC));
> +object_property_set_bool(OBJECT(s->digic), t
Also this patch adds initial support for Canon
PowerShot A1100 IS compact camera.
Signed-off-by: Antony Pavlov
---
hw/arm/Makefile.objs | 1 +
hw/arm/digic_boards.c | 88 +++
2 files changed, 89 insertions(+)
create mode 100644 hw/arm/digic_boar
14 matches
Mail list logo
