From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] xtensa noMMU support
Date: Thu, 31 Mar 2016 16:36:05 +0200 [thread overview]
Message-ID: <20160331163605.51afd1dc@free-electrons.com> (raw)
In-Reply-To: <CAMo8Bf+D8=R3bhnpqqPGmchKeE-QitgewSr59DDkv7tNJ1WsAw@mail.gmail.com>
Hello,
On Thu, 31 Mar 2016 06:20:51 +0300, Max Filippov wrote:
> > Is this actually the case?
>
> The following patch would switch to elf2flt version that has xtensa support:
> https://patchwork.ozlabs.org/patch/599708/
Ah, ok. I need to respin this series then.
> But I realize that elf2flt build is not enabled for xtensa, even with the
> above patch. I'll send a fix that enables it.
Seen your patch, thanks!
> It is possible to run noMMU kernel and userspace on MMUv3 cores
> with the mainline QEMU. Real noMMU cores need a fix that wasn't
> accepted to the QEMU mainline:
> http://qemu.11.n7.nabble.com/PATCH-0-3-target-xtensa-xtfpga-support-cores-without-MMU-td358668.html
> I probably need to get back to it and make suggested changes.
OK.
Do you think you could submit a minimal defconfig that creates a noMMU
Xtensa system that runs under Qemu? I think it would be quite useful,
as it would the first noMMU Qemu configuration that we would have in
Buildroot.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-31 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 15:27 [Buildroot] [PATCH 0/2] xtensa noMMU support Max Filippov
2016-03-17 15:27 ` [Buildroot] [PATCH 1/2] gcc: add xtensa uClinux support Max Filippov
2016-03-17 15:27 ` [Buildroot] [PATCH 2/2] uclibc: enable linuxthreads for xtensa Max Filippov
2016-03-31 1:57 ` [Buildroot] [PATCH 0/2] xtensa noMMU support Thomas Petazzoni
2016-03-31 3:20 ` Max Filippov
2016-03-31 14:36 ` Thomas Petazzoni [this message]
2016-03-31 17:52 ` Max Filippov
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=20160331163605.51afd1dc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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