Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] commits for yocto.git tree for x32 work
Date: Wed, 13 Jul 2011 07:38:28 -0700	[thread overview]
Message-ID: <4E1DADE4.9040100@gmail.com> (raw)
In-Reply-To: <1310556033.20015.1104.camel@rex>

On 07/13/2011 04:20 AM, Richard Purdie wrote:
> On Tue, 2011-07-12 at 12:02 -0700, nitin.a.kamble@intel.com wrote:
>> From: Nitin A Kamble<nitin.a.kamble@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@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




      parent reply	other threads:[~2011-07-13 14:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-12 19:02 [PATCH 0/5] commits for yocto.git tree for x32 work nitin.a.kamble
2011-07-12 19:02 ` [PATCH 1/5] siteinfo.bbclass: hack for x32 nitin.a.kamble
2011-07-13  6:20   ` Khem Raj
2011-07-13 15:41     ` Kamble, Nitin A
2011-07-14 19:49       ` Khem Raj
2011-07-12 19:02 ` [PATCH 2/5] udev-172: add a newer version for newer kernel nitin.a.kamble
2011-07-13  6:22   ` Khem Raj
2011-07-13  6:59     ` Koen Kooi
2011-07-13 15:43       ` Kamble, Nitin A
2011-07-12 19:02 ` [PATCH 3/5] runqemu: support qemux32 machine nitin.a.kamble
2011-07-13  1:35   ` Bruce Ashfield
2011-07-12 19:02 ` [PATCH 4/5] kernel.bbclass: fix the broken lines nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-12 19:02 ` [PATCH 5/5] glibc: fix false failure nitin.a.kamble
2011-07-13 11:16   ` Richard Purdie
2011-07-13 11:20 ` [PATCH 0/5] commits for yocto.git tree for x32 work Richard Purdie
2011-07-13 14:14   ` Tom Rini
2011-07-13 14:38   ` Khem Raj [this message]

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=4E1DADE4.9040100@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox