Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] imx-lib: new package
Date: Mon, 17 Dec 2012 21:44:21 +0100	[thread overview]
Message-ID: <87mwxc76je.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <50CF5987.90805@mind.be> (Arnout Vandecappelle's message of "Mon,  17 Dec 2012 18:42:31 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 Arnout> On 17/12/12 14:48, Arnout Vandecappelle (Essensium/Mind) wrote:
 >> +if BR2_PACKAGE_IMX_LIB
 >> +choice
 >> +	prompt "i.MX platform"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX25_3STACK
 >> +	bool "imx25-3stack"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX27ADS
 >> +	bool "imx27ads"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX37_3STACK
 >> +	bool "imx37-3stack"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX50
 >> +	bool "imx50"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX51
 >> +	bool "imx51"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX53
 >> +	bool "imx53"
 >> +
 >> +config BR2_PACKAGE_IMX_LIB_PLATFORM_IMX6Q
 >> +	bool "imx6q"
 >> +
 >> +endchoice

 Arnout>  Here's a second issue that I'd like to get some feedback on:
 Arnout> gst-fsl-plugins also uses a PLATFORM definition, but the list of
 Arnout> platforms is slightly different:
 Arnout> MX28/MX233/MX25/MX27/MX31/MX35/MX37/MX51/MX53/MX50/MX5X/MX6

 Arnout>  Ideally the 'platform' should be defined only once, but where? Or
 Arnout> should I add all the platforms to gst-fsl-plugins with a select of the
 Arnout> appropriate imx-lib platform?

We once talked about adding a SoC selection to buildroot, but decided it
would be too much effort to maintain.

Is the gst-fsl-plugins stuff still needed now that the coda driver is in
mainline?

 Arnout>  I can only test the mx6q because that's the only one for which
 Arnout> I have a board... Build-testing doesn't make a difference
 Arnout> because all platforms use the same API.

I have access to mx28 / mx51 / mx53 / mx6q boards and could do some
testing during christmas.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2012-12-17 20:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 13:48 [Buildroot] [PATCH] imx-lib: new package Arnout Vandecappelle
2012-12-17 15:50 ` Arnout Vandecappelle
2012-12-17 15:57   ` Benoît Thébaudeau
2012-12-17 17:27     ` Arnout Vandecappelle
2012-12-17 19:40       ` Benoît Thébaudeau
2012-12-17 21:49         ` Arnout Vandecappelle
2012-12-17 22:08           ` Benoît Thébaudeau
2012-12-17 16:01   ` Peter Korsgaard
2012-12-17 17:33     ` Arnout Vandecappelle
2012-12-17 20:42       ` Peter Korsgaard
2012-12-17 15:50 ` Benoît Thébaudeau
2012-12-18 10:06   ` Arnout Vandecappelle
2012-12-17 17:42 ` Arnout Vandecappelle
2012-12-17 20:44   ` Peter Korsgaard [this message]
2012-12-17 22:01     ` Arnout Vandecappelle
2012-12-17 22:12       ` Benoît Thébaudeau
2012-12-17 22:16         ` Arnout Vandecappelle
2012-12-17 22:49           ` Benoît Thébaudeau

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=87mwxc76je.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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