From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2 of 2] Introduction of Amlogic platform to buildroot
Date: Sat, 2 Nov 2013 16:54:59 +0100 [thread overview]
Message-ID: <20131102165459.09a35044@skate> (raw)
In-Reply-To: <l53633$d6q$3@ger.gmane.org>
Dear Stanislav Vasic,
On Sat, 2 Nov 2013 15:35:00 +0000 (UTC), Stanislav Vasic wrote:
> From 674615f2986c928cadd122377bbb4254192f5923 Mon Sep 17 00:00:00 2001
> From: Stanislav Vasic <svlasic@gmail.com>
> Date: Sat, 2 Nov 2013 16:07:38 +0100
> Subject: [PATCH] Introduce Amlogic MX platform to buildroot
>
> Target platform options submenu added, currently used
> only for setting up proper configuration of buildroot
> for Amlogic MX platform.
I'm afraid, but we don't want to have per-SoC options in Buildroot. We
have discussed this in the past, and there are way too many ARM SoC to
make this reasonable. Why is this patch needed at all?
For all other ARM platforms, the user simply has to choose the
appropriate ARM core (Cortex-A8, Cortex-A9, Cortex-A15, etc.), and
that's it. We also provide default configurations (see the configs/
directory) for various well-known hardware platforms, and those
configurations correctly define which ARM core should be used.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-02 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADYw_J+dw+E6xCosXu=hOo172ZPu1QJgtVTrHmJEQ2eVa6BWWg@mail.gmail. com>
2013-11-02 15:34 ` [Buildroot] [PATCH 1 of 2] Introduction of Amlogic platform to buildroot Stanislav Vasic
2013-11-02 15:36 ` Thomas Petazzoni
2013-11-02 15:35 ` [Buildroot] [PATCH 2 " Stanislav Vasic
2013-11-02 15:54 ` Thomas Petazzoni [this message]
2013-11-02 16:10 ` Stanislav Vasic
2013-11-02 16:20 ` Thomas Petazzoni
2013-11-02 20:49 ` Stanislav Vasic
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=20131102165459.09a35044@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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