From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stanislav Vasic Date: Sat, 2 Nov 2013 16:10:16 +0000 (UTC) Subject: [Buildroot] [PATCH 2 of 2] Introduction of Amlogic platform to buildroot References: <20131102165459.09a35044@skate> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Sat, 02 Nov 2013 16:54:59 +0100, Thomas Petazzoni wrote: > 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 >> 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? Hi, That is what I was told yesterday (about adding it). Amlogic buildroot is too complicated and it's used mainly for running XBMC on top of buildroot. I agree there are too many things (such as non-standard opengl drivers, Amlogic property a/v libraries...). Patch is needed so we know we're building for Amlogic SoC, and for other packages to know which eg. opengl or a/v libs to include in build. > 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. See above, at this point it's not so simple for Amlogic. > Best regards, > > Thomas Regards, Stan