From: Tom Rini <trini@konsulko.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
maemo-leste@lists.dyne.org, u-boot@lists.denx.de,
Merlijn Wajer <merlijn@wizzup.org>
Subject: Re: [maemo-leste] [PATCH] arm: Remove nokia_rx51 board
Date: Wed, 16 Jun 2021 17:20:20 -0400 [thread overview]
Message-ID: <20210616212020.GB9516@bill-the-cat> (raw)
In-Reply-To: <20210616211632.xxoo3vu6mlyxg5wr@pali>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Wed, Jun 16, 2021 at 11:16:32PM +0200, Pali Rohár wrote:
> On Wednesday 16 June 2021 17:12:13 Tom Rini wrote:
> > Wait, why is thumb disabled? That's something I'd really like to know
> > why on as my first guess is there's units with old enough cores that
> > have some thumb errata maybe?
>
> IIRC we disabled at time when N900 support was merged into U-Boot (about
> 10 years ago) as built binary did not work on real N900 HW. Non-thumb
> build work fine.
>
> I thought it was due to thumb errata but yesterday I was told that thumb
> errata affects running system only when virtual memory and context
> switches are used. And correct me if I'm wrong, but u-boot is not using
> virtual memory mapping and neither multiprocessing context switches.
>
> So it looks like that at that time (10 years ago) there was another bug
> in u-boot which caused that thumb build was non-working.
Thanks for explaining, yes, we should be able to enable thumb and
disable EFI and see just how close things are again to the size limit.
Oh, and we have things set such that the hooks to cause link time errors
on size overflow are enabled here, right?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-06-16 21:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 1:26 [PATCH] arm: Remove nokia_rx51 board Tom Rini
2021-05-19 13:27 ` Pali Rohár
2021-05-19 14:27 ` Oleh Kravchenko
2021-05-19 15:03 ` Pali Rohár
2021-05-19 15:52 ` Tom Rini
2021-05-21 14:44 ` Tom Rini
2021-05-21 21:36 ` Pali Rohár
2021-05-21 22:26 ` Tom Rini
2021-06-15 5:40 ` [maemo-leste] " Ivaylo Dimitrov
2021-06-15 12:34 ` Tom Rini
2021-06-16 6:02 ` Ivaylo Dimitrov
2021-06-16 11:52 ` Adam Ford
2021-06-16 11:55 ` Pali Rohár
2021-06-16 12:10 ` Tom Rini
2021-06-16 12:13 ` Tom Rini
2021-06-16 17:25 ` Ivaylo Dimitrov
2021-06-16 17:37 ` Tom Rini
2021-06-16 20:44 ` Merlijn Wajer
2021-06-16 21:16 ` Tom Rini
2021-06-16 21:03 ` Ivaylo Dimitrov
2021-06-16 21:12 ` Tom Rini
2021-06-16 21:16 ` Pali Rohár
2021-06-16 21:20 ` Tom Rini [this message]
2021-06-16 21:35 ` Pali Rohár
2021-06-17 7:18 ` Ivaylo Dimitrov
2021-06-17 18:21 ` Tom Rini
2021-06-16 17:21 ` Ivaylo Dimitrov
2021-05-19 19:06 ` Pavel Machek
2021-05-19 20:02 ` Tom Rini
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=20210616212020.GB9516@bill-the-cat \
--to=trini@konsulko.com \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=maemo-leste@lists.dyne.org \
--cc=merlijn@wizzup.org \
--cc=pali@kernel.org \
--cc=u-boot@lists.denx.de \
/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