Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 17:20:23 +0100	[thread overview]
Message-ID: <20131102172023.6a8bc642@skate> (raw)
In-Reply-To: <l53858$d6q$4@ger.gmane.org>

Dear Stanislav Vasic,

On Sat, 2 Nov 2013 16:10:16 +0000 (UTC), Stanislav Vasic wrote:

> 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...).

That's not a problem. We already have a number of packages with OpenGL
drivers for specific platforms:

 package/freescale-imx/gpu-viv-bin-mx6q/ (for i.MX6)
 package/rpi-userland/ (for Rasberry Pi)
 package/sunxi-mali/ (for Allwinner)
 package/ti-gfx/ (for TI OMAP)

> 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.

Just do it the way we do it for all of the platforms mentioned above:
add a package in Buildroot, and make it depend on BR2_arm. This way it
will only be visible on ARM platforms, and from this point, users are
expected to know which OpenGL implementation they need for their
platform.

We are also considering adding "demo" defconfigs in Buildroot so that
users could easily find a configuration that enables OpenGL for a given
platform.

> > 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.

See above. Amlogic is not exceptional: it's just like several other
SoCs we already support in Buildroot :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-11-02 16:20 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
2013-11-02 16:10     ` Stanislav Vasic
2013-11-02 16:20       ` Thomas Petazzoni [this message]
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=20131102172023.6a8bc642@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