From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] i.MX6: Update Freescale hardware-acceleration bits to latest versions
Date: Tue, 1 Oct 2013 21:42:47 +0200 [thread overview]
Message-ID: <20131001214247.5bdcaecb@skate> (raw)
In-Reply-To: <524A69BF.9080906@mind.be>
Dear Arnout Vandecappelle,
On Tue, 01 Oct 2013 08:20:47 +0200, Arnout Vandecappelle wrote:
> > By following the lead of the meta-fsl-arm project and allowing the first
> > of any packages with the Freescale EULA to prompt the user for
> > acceptance, but I'm not sure how to accomplish that.
> >
> > In the Yocto world, a tag ("ACCEPT_FREESCALE_EULA") placed in local.conf
> > is sufficient to bypass the prompt, which requires action by the user.
>
> We prefer to avoid that the build stops after half an hour or so
> because it is waiting for user input. Also, I don't see a reason why we
> have to explicitly ask the user to accept this license. If we do that, we
> should probably do the same for all the other packages.
>
> If we do want explicit acceptance, then it can be done similar to the
> Qt license, i.e. add a config option that enables the --auto-accept.
Agreed.
> > Agreed. I'm also confused about why this isn't in the freescale-imx/
> > directory.
>
> Because the libfslcodec fits in the multimedia libraries menu more than
> in the hardware handling menu.
I don't quite agree here. The location of the package in the menu has
nothing to do with the location of the package .mk file and directory.
So if the libfslcodec is downloaded from the same site and with the
same version as the other package/freescale-imx/ stuff and therefore
re-use the same variables, it could very well be moved under this
directory.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2013-10-01 19:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 19:07 [Buildroot] [PATCH 0/4] i.MX6 and Nitrogen6x updates Eric Nelson
2013-09-25 19:07 ` [Buildroot] [PATCH 1/4] nitrogen6x: bump U-Boot to latest production version (2013.07) Eric Nelson
2013-09-26 19:19 ` Peter Korsgaard
2013-09-25 19:07 ` [Buildroot] [PATCH 2/4] nitrogen6x: use 6x_bootscript/6x_upgrade instead of older 6q_ versions Eric Nelson
2013-09-26 14:37 ` Peter Korsgaard
2013-09-26 15:13 ` Eric Nelson
2013-09-26 19:10 ` Peter Korsgaard
2013-09-26 20:20 ` Eric Nelson
2013-09-26 19:20 ` Peter Korsgaard
2013-09-25 19:07 ` [Buildroot] [PATCH 3/4] nitrogen6x: bump kernel to latest version (3.0.35-4.1.0) Eric Nelson
2013-09-26 19:20 ` Peter Korsgaard
2013-09-25 19:07 ` [Buildroot] [PATCH 4/4] i.MX6: Update Freescale hardware-acceleration bits to latest versions Eric Nelson
2013-09-26 19:36 ` Peter Korsgaard
2013-09-26 20:41 ` Eric Nelson
2013-10-01 6:20 ` Arnout Vandecappelle
2013-10-01 14:07 ` Eric Nelson
2013-10-01 19:42 ` Thomas Petazzoni [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=20131001214247.5bdcaecb@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