Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [oe-commits] Tim 'timtim' Ellis : linux-orion: Add kernel for Marvell Orion based devices (replaces linux-linkstationarm) , initially supporting:
Date: Sat, 17 Jan 2009 21:29:13 +0100	[thread overview]
Message-ID: <gktf2p$thm$1@ger.gmane.org> (raw)
In-Reply-To: <200901172122.25511.openembedded@haerwu.biz>

On 17-01-09 21:22, Marcin Juszkiewicz wrote:
> On Saturday 17 of January 2009 13:33:01 GIT User account wrote:
>> Module: openembedded.git
>> Branch: org.openembedded.dev
>> Commit: 5f7f10f181bdc127786fce9a43e4ca71ae4ab03c
>> URL:
>> http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=5f7f10f
>> 181bdc127786fce9a43e4ca71ae4ab03c
>>
>> Author: Tim 'timtim' Ellis<tim.ellis@foonas.org>
>> Date:   Sat Jan 17 12:28:42 2009 +0000
>>
>> linux-orion: Add kernel for Marvell Orion based devices (replaces
>
> Few problems:
>
> 1. KERNEL_IMAGETYPE = "uImage" - this should be rather in machine config
> 2. You use linux-2.6.27.10.tar.bz2 - please change it to 2.6.27 tarball
>     with 2.6.27.10 patch added. It will save bandwidth for autobuilders
>     which usually have 2.6.27 already fetched for other devices.

   3. It looks like it can reuse linux_2.6.27.bb


> This also shows that we should merge linux.inc more into
> kernel.bbclass...

True.

regards,

Koen




      reply	other threads:[~2009-01-17 20:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090117123304.79177189331@amethyst.openembedded.net>
2009-01-17 20:22 ` [oe-commits] Tim 'timtim' Ellis : linux-orion: Add kernel for Marvell Orion based devices (replaces linux-linkstationarm) , initially supporting: Marcin Juszkiewicz
2009-01-17 20:29   ` Koen Kooi [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='gktf2p$thm$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox