On Tue, Jan 23, 2018 at 12:22 PM, Peter Maydell
wrote:
> On 23 January 2018 at 11:13, bzt bzt wrote:
> > There's a huge misunderstanding here. I have a working qemu for about
> half a
> > year now, and I don't need it merged. It's not my goal to submit a patch
Hi,
On Mon, Jan 22, 2018 at 1:12 PM, Peter Maydell
wrote:
> On 18 January 2018 at 21:39, bzt bzt wrote:
> > Dear All,
> >
> > Since you still haven't merged Alistair's patch, I decided to include it
> in
> > my own.
> > I've shrinked t
On Mon, Jan 22, 2018 at 12:41 PM, BALATON Zoltan wrote:
> Hello,
>
> On Thu, 18 Jan 2018, bzt bzt wrote:
>
>> Since you still haven't merged Alistair's patch, I decided to include it
>> in
>> my own.
>>
>
> Which patch exactly are you referr
+mc->max_cpus = BCM2836_NCPUS;
+ mc->min_cpus = BCM2836_NCPUS;
+mc->default_cpus = BCM2836_NCPUS;
+mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-a53");
+mc->default_ram_size = 1024 * 1024 * 1024;
+mc->ignore_memory_transaction_failures = true;
+};
On Tue, Nov 28, 2017 at 6:54 PM, Andrew Baumann <
andrew.baum...@microsoft.com> wrote:
> > From: bzt bzt [mailto:bztem...@gmail.com]
> > Sent: Tuesday, 28 November 2017 03:27
>
> > Yes, I agree. I've provided a parameterised version on Oct 24, which
> d
On Tue, Nov 28, 2017 at 12:56 PM, Peter Maydell
wrote:
> On 28 November 2017 at 11:26, bzt bzt wrote:
> > (Although I have a question. I'm not sure what's the preferred
> > way to get MachineClass* object in bcm2836. Use a MachineState* cast on
> it's
> >
Hi Andrew!
[...]
>
> In that case, IIRC my high-level suggestion was to either parameterise
> bcm2836 to take a CPU model string, or else move the CPU creation out of
> bcm2836.c into the board file. From what I've understood thus far about
> pi3, it does not seem necessary to have a separate bcm
Dear Andrew,
A month passed, and the maintainers didn't gave a damn about raspi3 support
in qemu. Any ideas?
On Wed, Oct 25, 2017 at 10:52 AM, bzt bzt wrote:
> Hi Andrew!
>
> On Tue, Oct 24, 2017 at 6:44 PM, Andrew Baumann <
> andrew.baum...@microsoft.com> wrote:
Hi Andrew!
On Tue, Oct 24, 2017 at 6:44 PM, Andrew Baumann <
andrew.baum...@microsoft.com> wrote:
[...]
> I see. The address space size sounds like it would affect the SoC
> (although is there really 40 bits of usable physical address space beyond
> the core?). If it's like pi2, however, the wifi
On Tue, Oct 24, 2017 at 1:05 PM, BALATON Zoltan wrote:
[...]
> Summa summarum, which one is preferred? Think of the future or keep it at a
>> bare minimum?
>>
>
> I don't feel I have a deciding word in this but to share my opinion I
> think it's better to keep it in one file avoiding too much cod
Hi Andrew!
On Mon, Oct 23, 2017 at 6:34 PM, Andrew Baumann <
andrew.baum...@microsoft.com> wrote:
> > From: Qemu-devel On Behalf Of bzt bzt
> > Sent: Sunday, 22 October 2017 06:21
> >
> > I've added support for "-M raspi3" to qemu. This is my first p
> eg:
> bcm2835: checking that the parameters are valid
> adding bcm2837
> adding raspi3
> etc..
>
> And you should run your patch through ./script/checkpatch.
>
> See: https://wiki.qemu.org/Contribute/SubmitAPatch
>
> Thanks,
> Fred
>
>
> On 10/22/2017 03:2
Dear All,
I've added support for "-M raspi3" to qemu. This is my first patch, I hope
it's okay. The github repo is here: https://github.com/bztsrc/qemu-raspi3
in case my patch does not work for some reason.
>From 1f10f957b57f336728097803bf8339a5577dd3c2 Mon Sep 17 00:00:00 2001
From: bzt
Date: S
13 matches
Mail list logo
