From: Marcel Ziswiler <marcel.ziswiler@toradex.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot PXA support
Date: Tue, 21 May 2019 10:33:39 +0000 [thread overview]
Message-ID: <233e768bbc3a33aca8ef9d4ec3520ce71cc8895f.camel@toradex.com> (raw)
In-Reply-To: <CALxOYEbNOsh657SFd=8ZbsJjoyt-_VQx=OdNZxpXzoH0V7bhrA@mail.gmail.com>
On Tue, 2019-05-21 at 12:50 +0300, Alex Sadovsky wrote:
> It's slightly off-topic but I wonder whether this ongoing deprecation
> of ARMv4 and ARMv5 (first in GCC, then in U-Boot) really simplifies
> anything at all.
> There are tons of devices that are still working good and there are
> even ARMv5-based MCUs that are still produced (such as CH561
> manufactured by WCH).
Please note that as of today Marvell is also still producing them PXAs
which are not to go end-of-life before later next year I believe.
> IMHO it makes sense to drop only the XScale-specific tuning first and
> to treat PXA (and similar CPUs) as a more generic armv5te. I wonder
> what to do when GCC drops ARMv5 completely...
I believe it was only an issue with early gcc 8 but does work just fine
again with later 8.2 or 8.3 versions.
However, what is more concerning to me is that in today's convoluted
moloch known as U-Boot there may simply not be any space any more for
something truly embedded but somewhat limited like PXA based hardware.
next prev parent reply other threads:[~2019-05-21 10:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 13:26 [U-Boot] U-Boot PXA support Tom Rini
2019-05-09 14:02 ` Tom Rini
2019-05-09 14:56 ` Marek Vasut
2019-05-09 15:03 ` Vasily Khoruzhick
2019-05-09 15:12 ` Marek Vasut
2019-05-09 15:22 ` Tom Rini
2019-05-16 14:53 ` Marcel Ziswiler
2019-05-16 15:02 ` Marek Vasut
2019-05-21 8:44 ` Marcel Ziswiler
2019-05-21 9:50 ` Alex Sadovsky
2019-05-21 10:33 ` Marcel Ziswiler [this message]
2019-05-21 12:49 ` Marek Vasut
2019-05-21 14:29 ` Marcel Ziswiler
2019-05-21 14:34 ` Marek Vasut
2019-05-21 14:50 ` Tom Rini
2019-05-21 16:43 ` Simon Glass
2019-05-21 13:47 ` Tom Rini
2019-05-21 12:47 ` Marek Vasut
2019-05-21 13:47 ` Alex Sadovsky
2019-05-21 13:58 ` Tom Rini
2019-05-21 14:03 ` Marek Vasut
2019-05-21 12:51 ` Tom Rini
2019-05-16 17:49 ` Tom Rini
2019-05-17 14:46 ` Marcel Ziswiler
2019-05-29 14:12 ` Tom Rini
2019-05-30 9:14 ` Marcel Ziswiler
2019-05-30 9:29 ` Marek Vasut
2019-05-30 11:47 ` Marcel Ziswiler
2019-05-31 19:34 ` Marek Vasut
2019-05-30 10:45 ` Alex Sadovsky
2019-05-30 11:19 ` 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=233e768bbc3a33aca8ef9d4ec3520ce71cc8895f.camel@toradex.com \
--to=marcel.ziswiler@toradex.com \
--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