From: Daiane Angolini <daiane.angolini@freescale.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm PATCH 3/3] linux-fslc: Use KERNEL_EXTRA_ARGS instead of EXTRA_OEMAKE
Date: Thu, 18 Apr 2013 13:23:39 -0300 [thread overview]
Message-ID: <51701E0B.8010408@freescale.com> (raw)
In-Reply-To: <CAOMZO5AQQBbDKEmWu1GYysnPwTGuPK-jhu0YFzbdWhsC0MKH3Q@mail.gmail.com>
On 04/18/2013 12:42 PM, Fabio Estevam wrote:
> On Thu, Apr 18, 2013 at 10:12 AM, Otavio Salvador
> <otavio@ossystems.com.br> wrote:
>
>> # We need to pass it as param since kernel might support more then one
>> # machine, with different entry points
>> -EXTRA_OEMAKE += "LOADADDR=${UBOOT_ENTRYPOINT}"
>> +KERNEL_EXTRA_ARGS += "LOADADDR=${UBOOT_ENTRYPOINT}"
>
> Can't we put KERNEL_EXTRA_ARGS into a more common location?
>
> In 2/3 you placed it in linux-imx.inc, which covers 2.6.35/3.0.35
> kernels, but I am was wondering if you could make this applied for all
> the kernels generated by meta-fsl-arm.
Maybe POKY layer.
I'm not complete happy this is being handling by meta-fsl-arm
--
Daiane
next prev parent reply other threads:[~2013-04-18 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 13:12 [meta-fsl-arm PATCH 1/3] u-boot-fslc: Update to patches-2013.04's 20130415 snapshot based on 2013.04-rc3 Otavio Salvador
2013-04-18 13:12 ` [meta-fsl-arm PATCH 2/3] linux-imx.inc: Pass LOADADDRESS to kernel build Otavio Salvador
2013-04-18 13:12 ` [meta-fsl-arm PATCH 3/3] linux-fslc: Use KERNEL_EXTRA_ARGS instead of EXTRA_OEMAKE Otavio Salvador
2013-04-18 15:42 ` Fabio Estevam
2013-04-18 16:23 ` Daiane Angolini [this message]
2013-04-18 16:33 ` Otavio Salvador
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=51701E0B.8010408@freescale.com \
--to=daiane.angolini@freescale.com \
--cc=festevam@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.