Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
	Romain Naour <romain.naour@smile.fr>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Xtensa qemu nommu defconfig not working
Date: Mon, 28 Nov 2022 14:12:21 +0100	[thread overview]
Message-ID: <20221128141221.0b2f5a56@windsurf> (raw)
In-Reply-To: <CAMo8BfKE9KqDYyFhsKK9M8XjjuR=TtONT8JdKniFKwAgfr4HVg@mail.gmail.com>

On Mon, 28 Nov 2022 03:54:19 -0800
Max Filippov <jcmvbkbc@gmail.com> wrote:

> > Max, do you think you could have a look at what is happening?  
> 
> AFAICS the following commit in the elf2flt
> https://github.com/uclinux-dev/elf2flt/commit/5e08f19683163584f23b953e570749964758c439
> 
> disabled address endianness fixup for addresses in the text segment for
> xtensa which results in the observed failure. I haven't checked, but from
> the code it looks like not only the xtensa may be affected.
> I can confirm that reverting that change fixes xtensa nommu boot.

Thanks for the investigation. How do we move forward from this? I must
say I never went into the details of elf2flt, so I'm not sure how to
fix this myself.

Should we report a bug to upstream elf2flt (which are generally never
looked at), or is someone volunteering to provide a fix for this?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-28 13:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 18:11 [Buildroot] Xtensa qemu nommu defconfig not working Thomas Petazzoni via buildroot
2022-11-28 11:54 ` Max Filippov
2022-11-28 13:12   ` Thomas Petazzoni via buildroot [this message]
2022-11-28 13:37     ` Max Filippov
2022-12-27 13:53       ` Thomas Petazzoni via buildroot

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=20221128141221.0b2f5a56@windsurf \
    --to=buildroot@buildroot.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=niklas.cassel@wdc.com \
    --cc=romain.naour@smile.fr \
    --cc=thomas.petazzoni@bootlin.com \
    /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