On 5 August 2013 12:18, Peter Maydell wrote:
> From: John Rigby
>
> Add 'virt' platform support corresponding to arch/arm/mach-virt
> in the Linux kernel tree. This has no platform-specific code but
> can use any device whose kernel driver is is able to work purely
> from a device tree node. We u
On Mon, Aug 5, 2013 at 4:48 PM, Peter Maydell wrote:
> From: John Rigby
>
> Add 'virt' platform support corresponding to arch/arm/mach-virt
> in the Linux kernel tree. This has no platform-specific code but
> can use any device whose kernel driver is is able to work purely
> from a device tree no
On 5 August 2013 12:48, Anup Patel wrote:
>> +static const MemMapEntry a15memmap[] = {
>> +[VIRT_FLASH] = { 0, 0x10 },
>
> IMHO, 1 MB of flash is small for possible future expansion. If mach-virt
> becomes popular then we can expect people running UBoot or UEFI or
> from this flash.
>
On Mon, Aug 5, 2013 at 5:31 PM, Peter Maydell wrote:
> On 5 August 2013 12:48, Anup Patel wrote:
>>> +static const MemMapEntry a15memmap[] = {
>>> +[VIRT_FLASH] = { 0, 0x10 },
>>
>> IMHO, 1 MB of flash is small for possible future expansion. If mach-virt
>> becomes popular then we can exp
On 5 August 2013 13:22, Anup Patel wrote:
> On Mon, Aug 5, 2013 at 5:31 PM, Peter Maydell
> wrote:
>> On 5 August 2013 12:48, Anup Patel wrote:
+static const MemMapEntry a15memmap[] = {
+[VIRT_FLASH] = { 0, 0x10 },
>>>
>>> IMHO, 1 MB of flash is small for possible future expan
On Mon, Aug 5, 2013 at 5:58 PM, Peter Maydell wrote:
> On 5 August 2013 13:22, Anup Patel wrote:
>> On Mon, Aug 5, 2013 at 5:31 PM, Peter Maydell
>> wrote:
>>> On 5 August 2013 12:48, Anup Patel wrote:
> +static const MemMapEntry a15memmap[] = {
> +[VIRT_FLASH] = { 0, 0x10 },
>
On 5 August 2013 13:37, Anup Patel wrote:
> On Mon, Aug 5, 2013 at 5:58 PM, Peter Maydell
> wrote:
>> I really don't want to eat 2MB for each virtio-mmio transport
>> in a 32 bit address space, it seems hugely wasteful unless
>> there's a good reason to do it.
>
> I am not suggesting to give 2MB
