From: Paulo Matos <pmatos@igalia.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARM qemu versatile defconfig
Date: Wed, 18 Mar 2020 11:50:15 +0100 [thread overview]
Message-ID: <87pnda6ioo.fsf@igalia.com> (raw)
In-Reply-To: <20200318113447.709da855@windsurf.home>
Thomas Petazzoni writes:
> On Wed, 18 Mar 2020 11:31:16 +0100
> Paulo Matos <pmatos@igalia.com> wrote:
>
>> I am trying to get a emulation environment based on arm 32bits to
>> emulate the native environment we have setup with
>> raspberrypi3_defconfig.
>>
>> The only existing defconfig I can see that could help me with this is
>> qemu_arm_versatile_defconfig however, I do not understand what this
>> 'versatile' refers to or find any online documentation about it.
>>
>> Could someone explain what this 'versatile' defconfig corresponds to in
>> terms of emulated hardware? Or is it versatile because you should use
>> 'make menuconfig' later to specifically configure it for your needs?
>
> Versatile is one of the ARM machines emulated by Qemu. If you want to
> be closer to RPi3, I would suggest to use our
> qemu_arm_vexpress_defconfig instead, and follow the instructions of
> board/qemu/arm-vexpress/readme.txt to use it.
Oh! I just learned Versatile is actually an ARM trademark. I thought
versatile here was used as an adjective. :)
Thanks for the suggestion on vexpress - I will give this a go.
>
> Best regards,
>
> Thomas
prev parent reply other threads:[~2020-03-18 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 10:31 [Buildroot] ARM qemu versatile defconfig Paulo Matos
2020-03-18 10:34 ` Thomas Petazzoni
2020-03-18 10:50 ` Paulo Matos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnda6ioo.fsf@igalia.com \
--to=pmatos@igalia.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox