[OE-core] [PATCH 0/5] commits for yocto.git tree for x32 work

Khem Raj raj.khem at gmail.com
Wed Jul 13 14:38:28 UTC 2011


On 07/13/2011 04:20 AM, Richard Purdie wrote:
> On Tue, 2011-07-12 at 12:02 -0700, nitin.a.kamble at intel.com wrote:
>> From: Nitin A Kamble<nitin.a.kamble at intel.com>
>>
>> These are commits for yocto tree. I came up with as part of the x32 work.
>> I think these commits does not belong in the x32 layer and should go
>> in the yocto/oecore tree.
>>
>> The siteinfo.bbclass commit is a hacky way to get the the right siteinfo for
>> x32 now. In the future a better solution will be implemented for that purpose.
>>
>> The following changes since commit 7354fc9213f27aa1b643dbe88070437f1ee4c063:
>>
>>    insane.bbclass: skip rdepends QA checks for kernel / modules (2011-07-12 15:22:09 +0100)
>>
>> are available in the git repository at:
>>    git://git.pokylinux.org/poky-contrib nitin/x32
>>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/x32
>>
>> Nitin A Kamble (5):
>>    siteinfo.bbclass: hack for x32
>>    udev-172: add a newer version for newer kernel
>>    runqemu: support qemux32 machine
>
> These first three need a little more thought. They're fine to as proof
> of concept work but we need to find better ways to integrate them.
>
> Specifically:
>
> The siteinfo change is a hack and can't be merged as is. We need to find
> a way to change the target_arch or target_os in such a way we can signal
> to siteinfo to do something different. I also wonder if using i686-linux
> is actually correct for x32 in all cases since x32 does support 64 bit
> data types.

I think it should have its own bits in separate file.

>
> The udev update needs various other work as people have commented. We
> need to resolve the udev differences between meta-oe and oe-core.
>
> runqemu looks like it can be simplified as it looks like just the kernel
> name is different? Is x32 using a different machine config at present?
> Can we use the qemux86-64 machine directly and just add some tweaks to
> it? That would avoid the need to change the qemu scripting?
>
> Cheers,
>
> Richard
>
>
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





More information about the Openembedded-core mailing list