From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: Romain Naour <romain.naour@gmail.com>,
Giulio Benetti <giulio.benetti@benettiengineering.com>,
yann.morin.1998@free.fr, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/3] arch: add support for mcf5441x Colfdire
Date: Wed, 10 Apr 2024 21:56:56 +0200 [thread overview]
Message-ID: <20240410215656.1756a37e@windsurf> (raw)
In-Reply-To: <20240410171211.1633127-2-jeanmichel.hautbois@yoseli.org>
Hello,
On Wed, 10 Apr 2024 19:12:09 +0200
Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org> wrote:
> The m68k family ony has one Coldfire variant, namely the 5208. Add the
> support for the MCF5441x CPU family in the configuration file.
> This covers MCF54410, MCF54415, MCF54416, MCF54417 and MCF54418.
Interesting. I always thought that Coldfire meant "no MMU" and 68k
meant "MMU", but I was wrong. The family of 68k and coldfire is quite
messy, difficult to find clear and reliable sources of information.
> +config BR2_GCC_TARGET_ARCH
> + default "cf" if BR2_m68k_cf5441x
The problem with this is that "cf" is not a valid value for gcc -march=
option. Look at the documentation at:
https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/M680x0-Options.html
The valid values of -march are:
Permissible values of arch for M680x0 architectures are: ‘68000’,
‘68010’, ‘68020’, ‘68030’, ‘68040’, ‘68060’ and ‘cpu32’. ColdFire
architectures are selected according to Freescale’s ISA classification
and the permissible values are: ‘isaa’, ‘isaaplus’, ‘isab’ and
‘isac’.
What happens when you don't specify -march? Do you know which of isaa,
isaaplus, isab and isac the MCF5441x corresponds to?
Best regards,
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
next prev parent reply other threads:[~2024-04-10 19:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 17:12 [Buildroot] [PATCH v2 0/3] Add support for the MCF5441x Coldfire Jean-Michel Hautbois
2024-04-10 17:12 ` [Buildroot] [PATCH v2 1/3] arch: add support for mcf5441x Colfdire Jean-Michel Hautbois
2024-04-10 19:56 ` Thomas Petazzoni via buildroot [this message]
2024-04-10 21:08 ` Jean-Michel Hautbois
2024-04-10 21:17 ` Thomas Petazzoni via buildroot
2024-04-11 5:59 ` Jean-Michel Hautbois
2024-04-11 13:48 ` Jean-Michel Hautbois
2024-07-12 21:53 ` Romain Naour via buildroot
2024-09-18 8:27 ` Jean-Michel Hautbois
2024-04-10 17:12 ` [Buildroot] [PATCH v2 2/3] board: add the qemu board support for mcf54418 Jean-Michel Hautbois
2024-07-12 21:09 ` Romain Naour via buildroot
2024-04-10 17:12 ` [Buildroot] [PATCH v2 3/3] package/glibc: enable for coldfire with MMU Jean-Michel Hautbois
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=20240410215656.1756a37e@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=romain.naour@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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