[oe] RFC: Fix for bug 1744 and some restructuring of omap kernel bb files.

Philip Balister philip at balister.org
Thu Aug 23 09:49:49 UTC 2007


Is there any reason why you marked the linux-omap1_2.6.22 with 
DEFAULT_PREFERENCE = "-1" and removed the git kernels 
DEFAULT_PREFERENCE="-1"? I am guessing these are testing artifacts and 
am setting the git kernel to -1 and removing the DEFAULT_PREFERENCE from 
2.6.22.

Other than that, the patch looks good.

Philip

Khem Raj wrote:
> Hi Philip
> 
> Thanks for looking at it.
> 
> On 8/22/07, Philip Balister <philip at balister.org> wrote:
>> I have given it a quick look, and it looks reasonable. It appears to
>> drop OABI support, which I think is OK, except for the celinux distro
>> (not sure).
> 
> Infact it does not. Default config file has EABI disabled in
> defconfig. The logic in linux-omap.inc enables it if it detects an
> EABI capable toolchain.
> 
>> The only real concern I have is that we would like to move to the
>> linux.inc/linux_2.6.x.bb style of kernel bb files. Should we push this,
>> or wait until we can convert the omap/davinci kernels to linux.inc? I
>> shouldn't even look at this until September ...
> 
> I would say one step at a time. This patch is big enough so we should
> go towards it incrementally
> 
>> Philip
>>
>> Khem Raj wrote:
>>> Hi Koen et al.
>>>
>>> I have been looking into omap structure of late and found that it was
>>> hard to add a new machine to same kernel build without some
>>> duplication. So I went ahead and tried to fix it. Attached patch also
>>> fixes bug 1744.
>>>
>>> I have moved the defconf files to kernel-<version>/$MACHINE folder and
>>> I expect that we add machine specific patches if needed here too.
>>>
>>> I have built omap5912osk and omap2430sdp machine kernels with this
>>> change and they built and worked ok.
>>>
>>> However I have also made changes to other omap related files which I
>>> believe I correct but it would be helpful if someone could test them.
>>>
>>> I havent changed the old kernel bb files. If this looks ok and
>>> applicable I can do that too.
>>>
>>> Is it ok?
>>>
>>> Thanks
>>>
>>> -Khem
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel at lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>>
>>
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20070823/c6cf11ac/attachment-0002.bin>


More information about the Openembedded-devel mailing list