All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	Romain Naour <romain.naour@gmail.com>,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/3] Add support for the MCF54418 Coldfire
Date: Mon, 3 Jul 2023 21:01:12 +0200	[thread overview]
Message-ID: <20230703190112.GD2510@scaer> (raw)
In-Reply-To: <20230629053130.3976-1-jeanmichel.hautbois@yoseli.org>

Jean-Michel, All,

On 2023-06-29 07:31 +0200, Jean-Michel Hautbois spake thusly:
> I have a custom board which uses a MCF54418 and I want it to use an
> upstream buildroot (for all the good reasons ;-)).
> From what I can tell the only Coldfire processor currently supported is
> the MCF5208 which does not have a MMU.
> 
> While trying to add the processor support, I faced an issue during the
> host-gcc build when the MMU configuration is selected, because it makes
> it compile the multilib part.
> 
> Sadly, a commit [1] removed the GCC ARCH configuration which was used to
> determine if the architecture is "m68k" or "cf". I have re-introduced
> this configuration here, only for the MCF54418 case for now as I am not
> sure if it is my real issue or not. What I can tell is that when I have
> the BR2_USE_MMU selected, the host-gcc fails and it passes when I add
> the proper architecture.
> 
> [1]: eda11417be m68k: remove BR2_GCC_TARGET_ARCH

Since commit 1/3 will need a more detailed commit log, I've marked the
series as changes-requested on Patchwork. Which means that my comment
on patch 2/3 is mott: you have to squash commits 2 and three together
when you respin.

Regards,
Yann E. MORIN.

> Jean-Michel Hautbois (3):
>   arch: add support for mcf54418 Colfdire
>   board: add the qemu board support for mcf54418
>   configs: add support for the 54418 qemu defconfig
> 
>  arch/Config.in.m68k                   |  9 +++++++++
>  board/qemu/m68k-mcf54418/linux.config | 23 +++++++++++++++++++++++
>  configs/qemu_m68k_mcf54418_defconfig  | 19 +++++++++++++++++++
>  toolchain/Config.in                   |  1 +
>  4 files changed, 52 insertions(+)
>  create mode 100644 board/qemu/m68k-mcf54418/linux.config
>  create mode 100644 configs/qemu_m68k_mcf54418_defconfig
> 
> -- 
> 2.39.2
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-07-03 19:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  5:31 [Buildroot] [PATCH 0/3] Add support for the MCF54418 Coldfire Jean-Michel Hautbois
2023-06-29  5:31 ` [Buildroot] [PATCH 1/3] arch: add support for mcf54418 Colfdire Jean-Michel Hautbois
2023-07-03 18:55   ` Yann E. MORIN
2023-07-03 20:37     ` Jean-Michel Hautbois
2023-07-04  5:24       ` Yann E. MORIN
2023-07-03 19:03   ` Yann E. MORIN
2023-06-29  5:31 ` [Buildroot] [PATCH 2/3] board: add the qemu board support for mcf54418 Jean-Michel Hautbois
2023-07-03 18:42   ` Yann E. MORIN
2023-06-29  5:31 ` [Buildroot] [PATCH 3/3] configs: add support for the 54418 qemu defconfig Jean-Michel Hautbois
2023-07-03 19:01 ` Yann E. MORIN [this message]

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=20230703190112.GD2510@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=jeanmichel.hautbois@yoseli.org \
    --cc=romain.naour@gmail.com \
    --cc=thomas.de_schampheleire@nokia.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.