From: "Eric Bénard" <eric@eukrea.com>
To: Daiane Angolini <daiane.angolini@freescale.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm PATCH v2 3/3] linux-fslc: Refactor to use linux-imx.inc and avoid duplication of code
Date: Fri, 19 Apr 2013 14:10:19 +0200 [thread overview]
Message-ID: <20130419141019.48c97e06@e6520eb> (raw)
In-Reply-To: <5171292F.9020104@freescale.com>
Hi Daiane,
Le Fri, 19 Apr 2013 08:23:27 -0300,
Daiane Angolini <daiane.angolini@freescale.com> a écrit :
> On 04/18/2013 04:58 PM, Otavio Salvador wrote:
> > On Thu, Apr 18, 2013 at 4:51 PM, Daiane Angolini
> > <daiane.angolini@freescale.com> wrote:
> >> On 04/18/2013 03:59 PM, Otavio Salvador wrote:
> >>>
> >>> Provides a new linux-fslc.inc file which abstracts the specific
> >>> changes for the linux-fslc based kernels. A new variable has been add
> >>> to linux-imx.inc to allow to skip the 'imx-test' specific hacks after
> >>> kernel install as 'imx-test' is not supported for Linux mainline.
> >>>
> >>> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> >>> ---
> >>
> >> I understand what you did, but it's not yet a common place for both kernel
> >> recipes.
> >>
> >> If it is needed for *any* kernel, poky is wrong in not providing this for
> >> *any* kernel.
> >
> > Usually kernel would do the right thing but not in our case. Some
> > entry point are even not in the kernel code from FSL branch.
>
> I would accept this argument if we only faced this problem with FSL kernel.
>
> But, as we faced exactly the same with kernel mainline, I can't accept that.
>
> If kernel mainline is wrong, we must fix it.
>
when compiling manually a mainline kernel out of OE, you may have to do
the same thing if the .config includes several platforms which have a
different LOADADDR (example : i.MX51 where RAM is at 0x90000000 and
i.MX53 where it is at 0x70000000). That's not a bug that's the
consequence of having different architectures enabled at the same time
in the same defconfig.
Eric
next prev parent reply other threads:[~2013-04-19 12:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 18:59 [meta-fsl-arm PATCH v2 1/3] u-boot-fslc: Update to patches-2013.04's 20130415 snapshot based on 2013.04-rc3 Otavio Salvador
2013-04-18 18:59 ` [meta-fsl-arm PATCH v2 2/3] linux-imx.inc: Pass LOADADDRESS to kernel build Otavio Salvador
2013-04-18 18:59 ` [meta-fsl-arm PATCH v2 3/3] linux-fslc: Refactor to use linux-imx.inc and avoid duplication of code Otavio Salvador
2013-04-18 19:51 ` Daiane Angolini
2013-04-18 19:58 ` Otavio Salvador
2013-04-18 23:46 ` Fabio Estevam
2013-04-19 8:03 ` Eric Bénard
2013-04-19 11:26 ` Daiane Angolini
2013-04-19 12:01 ` Otavio Salvador
2013-04-19 12:26 ` Fabio Estevam
2013-04-19 12:36 ` Eric Bénard
2013-04-19 12:38 ` Daiane Angolini
2013-04-19 12:41 ` Otavio Salvador
2013-04-19 13:25 ` Daiane Angolini
2013-04-19 13:33 ` Otavio Salvador
2013-04-19 13:45 ` Daiane Angolini
2013-04-19 13:47 ` Otavio Salvador
2013-04-19 12:36 ` Daiane Angolini
2013-04-19 12:38 ` Otavio Salvador
2013-04-19 11:23 ` Daiane Angolini
2013-04-19 12:00 ` Otavio Salvador
2013-04-19 12:10 ` Eric Bénard [this message]
2013-04-19 12:34 ` Daiane Angolini
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=20130419141019.48c97e06@e6520eb \
--to=eric@eukrea.com \
--cc=daiane.angolini@freescale.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.