All of lore.kernel.org
 help / color / mirror / Atom feed
From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Fix uImage generation in way compatible	with	kernel.bbclass
Date: Wed, 28 Nov 2007 14:32:06 +0000	[thread overview]
Message-ID: <474D7BE6.6070907@xora.org.uk> (raw)
In-Reply-To: <474D707E.2000504@student.utwente.nl>

Koen Kooi wrote:
> Graeme Gregory schreef:
>> I would like to do the attached patch to linux.inc to change uImage
>> generation so it is compatible with the way kernel.bbclass does things.
> 
>> This means the uImage ends up in kernel-image not some random file
>> called uImage but not really a uImage.
> 
>> koen said the do_install_prepend stuff was to work around vendor bugs
>> and is no longer needed in this file.
> 
> Looks good, except for these bits of collateral damage:
> 
> -        if test -e arch/${ARCH}/boot/images/uImage ; then
> -             ln -f arch/${ARCH}/boot/images/uImage
> arch/${ARCH}/boot/uImage
> 
> The above is needed for various powerpc/ppc boards, and the below is
> needed for at least blackfin:
> 
> -        if test -e arch/${ARCH}/kernel/vmlinux.lds ; then
> -             ln -f arch/${ARCH}/kernel/vmlinux.lds
> arch/${ARCH}/boot/vmlinux
> 
> The linux kernel doesn't seem to have a strict policy on image placement
> and various vendor patches aren't exactly helping the situation :/
> 
Ok, I misunderstood you and thought they were all not needed lines, I
shall restore these two then.

Graeme




  reply	other threads:[~2007-11-28 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 11:47 [RFC] Fix uImage generation in way compatible with kernel.bbclass Graeme Gregory
2007-11-28 13:43 ` Koen Kooi
2007-11-28 14:32   ` Graeme Gregory [this message]
2007-11-28 14:36   ` Graeme Gregory
2007-11-28 15:55     ` Koen Kooi
2007-11-28 17:16       ` Graeme Gregory
2007-11-28 14:49   ` pHilipp Zabel
2007-11-29 11:29 ` Graeme Gregory

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=474D7BE6.6070907@xora.org.uk \
    --to=dp@xora.org.uk \
    --cc=openembedded-devel@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 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.