Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Romain Naour <romain.naour@gmail.com>,
	yann.morin.1998@free.fr, buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	linux-amarula@amarulasolutions.com,
	Ben Wolsieffer <Ben.Wolsieffer@hefring.com>
Subject: Re: [Buildroot] [PATCH v2 0/9] add ARM FDPIC support
Date: Sun, 22 Sep 2024 12:14:31 +0200	[thread overview]
Message-ID: <20240922121431.3fa71502@windsurf> (raw)
In-Reply-To: <20240922092312.2061358-1-dario.binacchi@amarulasolutions.com>

Hello Dario,

On Sun, 22 Sep 2024 11:23:03 +0200
Dario Binacchi <dario.binacchi@amarulasolutions.com> wrote:

> Dario Binacchi (1):
>   configs/stm32f746_disco_sd: new defconfig

Aside from this defconfig, it would be really nice to have a defconfig
that allows to test ARM noMMU (both FLAT and FDPIC) with Qemu. Could
you, and perhaps Waldemar, check what the options are? I had a quick
look, and it doesn't seem obvious which ARM noMMU platform supported by
Qemu is also supported by Linux. I vaguely remember at some point that
the versatile (or vexpress?) platforms allowed to boot a noMMU system,
but I'm not 100% sure.

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

  parent reply	other threads:[~2024-09-22 10:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22  9:23 [Buildroot] [PATCH v2 0/9] add ARM FDPIC support Dario Binacchi
2024-09-22  9:23 ` [Buildroot] [PATCH v2 1/9] Revert: "arch: drop now useless support for FDPIC" Dario Binacchi
2024-09-22  9:23 ` [Buildroot] [PATCH v2 2/9] arch: don't enable FDPIC binaries by default Dario Binacchi
2024-09-22  9:23 ` [Buildroot] [PATCH v2 3/9] arch: make FDPIC dependent on toolchain support Dario Binacchi
2024-09-22 10:06   ` Thomas Petazzoni via buildroot
2024-09-22  9:23 ` [Buildroot] [PATCH v2 4/9] arch/arm: add support for FDPIC Dario Binacchi
2024-09-22 10:08   ` Thomas Petazzoni via buildroot
2024-09-22  9:23 ` [Buildroot] [PATCH v2 5/9] boot/uboot: pass -mno-fdpic if FDPIC is enabled Dario Binacchi
2024-09-22 10:10   ` Thomas Petazzoni via buildroot
2024-09-22  9:23 ` [Buildroot] [PATCH v2 6/9] linux: " Dario Binacchi
2024-09-22  9:23 ` [Buildroot] [PATCH v2 7/9] package/uclibc: enable NPTL on no-MMU ARM w/ FDPIC Dario Binacchi
2024-09-22  9:23 ` [Buildroot] [PATCH v2 8/9] package/busybox: remove STATIC from busybox-minimal.config Dario Binacchi
2024-09-22  9:23 ` [Buildroot] [PATCH v2 9/9] configs/stm32f746_disco_sd: new defconfig Dario Binacchi
2024-09-22 10:14 ` Thomas Petazzoni via buildroot [this message]
2024-09-22 15:36   ` [Buildroot] [PATCH v2 0/9] add ARM FDPIC support Waldemar Brodkorb

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=20240922121431.3fa71502@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Ben.Wolsieffer@hefring.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=linux-amarula@amarulasolutions.com \
    --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