Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Fazio <vfazio@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2 1/1] arch/Config.in.x86: consolidate Geode CPU targets
Date: Tue, 1 Aug 2023 23:18:37 +0200	[thread overview]
Message-ID: <20230801231837.25545d7c@windsurf> (raw)
In-Reply-To: <20230801171012.1652426-1-vfazio@gmail.com>

On Tue,  1 Aug 2023 12:10:12 -0500
Vincent Fazio <vfazio@gmail.com> wrote:

> Since its introduction in 7d8a59b40, the BR2_x86_geode CPU target has
> pointed to GCC -march=geode which targets AMD Geode processors [0].
> 
> This arch tuning enables MMX and 3DNow! extensions in GCC but these are
> not currently reflected in the selected flags by BR2_x86_geode.
> 
> This is likely due to the confusing naming and history of "Geode".
> 
> The AMD Geode can trace its origins back to the Cyrix MediaGXm [1] and
> then to the NSC Geode GXm/GXLV/GX1/GX2 [2]. All of these processors have
> MMX instruction support listed in their datasheets. The NSC GX2 was the
> first in the series to enable 3DNow!.
> 
> When 7fed07d3a4a introduced BR2_X86_CPU_HAS_MMX, Geode was skipped
> presumably because it wasn't clear that the target is AMD Geode and
> because the Wikipedia documentation for Geode is incomplete [2] with
> regards to supported instructions as they all support MMX.
> 
> When f6cd56b9ce3 introduced BR2_X86_CPU_HAS_3DNOW, Geode was skipped
> presumably for similar reasons.
> 
> Note: the in-tree olpc_xo1_defconfig uses BR2_x86_geode which is fine
> as this hardware uses the AMD Geode [3].
> 
> Make it more clear that the target is AMD Geode by renaming the Kconfig
> menu option and add both MMX and 3DNow! flags to BR2_x86_geode.
> 
> [0]: https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=gcc/config/i386/geode.md;;hb=HEAD
> [1]: https://en.wikipedia.org/wiki/MediaGX#MediaGXm
> [2]: https://en.wikipedia.org/wiki/Geode_%28processor%29
> [3]: https://wiki.laptop.org/go/Hardware_specification
> 
> Signed-off-by: Vincent Fazio <vfazio@gmail.com>
> ---
> Changes v1 -> v2:
>   - Reword the commit message
> ---
>  arch/Config.in.x86 | 16 ++--------------
>  1 file changed, 2 insertions(+), 14 deletions(-)

I have further extended the commit log to explain that
BR2_x86_geode_mmx is removed, and that we don't need legacy handling
for this removal, as this option has never been part of a released
version of Buildroot.

Applied with this tweak. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2023-08-01 21:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 22:47 [Buildroot] [PATCH 1/1] arch/Config.in.x86: consolidate AMD Geode CPU targets Vincent Fazio
2023-08-01 17:10 ` [Buildroot] [PATCH v2 1/1] arch/Config.in.x86: consolidate " Vincent Fazio
2023-08-01 21:18   ` Thomas Petazzoni via buildroot [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=20230801231837.25545d7c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vfazio@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox