Re: [meta-fsl-arm PATCH v2 3/3] linux-fslc: Refactor to use linux-imx.inc and avoid duplication of code

[Daiane Angolini <daiane.angolini@freescale.com>]

On 04/19/2013 09:10 AM, Eric Bénard wrote:
> 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.

Which only ensure that FSL kernel is not wrong the same way mainline is 
not wrong.



-- 
Daiane