All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: Fix for bug 1744 and some restructuring of omap	kernel bb files.
Date: Thu, 23 Aug 2007 05:49:49 -0400	[thread overview]
Message-ID: <46CD583D.7020402@balister.org> (raw)
In-Reply-To: <19c1b8a90708221012m446c3157ya692e916c5270da2@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2797 bytes --]

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@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@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>>
>>
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2007-08-23  9:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 15:52 RFC: Fix for bug 1744 and some restructuring of omap kernel bb files Khem Raj
2007-08-22 16:51 ` Philip Balister
2007-08-22 17:12   ` Khem Raj
2007-08-23  9:49     ` Philip Balister [this message]
2007-08-23 18:24       ` Khem Raj
2007-08-22 17:22   ` Marcin Juszkiewicz

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=46CD583D.7020402@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.