All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: [RFC] Fix uImage generation in way	compatible	with	kernel.bbclass
Date: Wed, 28 Nov 2007 16:55:15 +0100	[thread overview]
Message-ID: <474D8F63.6000401@student.utwente.nl> (raw)
In-Reply-To: <474D7D09.4090702@xora.org.uk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Graeme Gregory schreef:
> Koen Kooi wrote:
>  > 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
>>
> Actually isnt this bolloxed anyway by regenerating the uImage
> in do_deploy?

It is, I think we can fix it in your shiny new do_compile_append method :)
And pH5 is partly right about the linker script, I checked and in newer
revisions the .lds file is indeed a linker script.

regards,

Koen

- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHTY9jMkyGM64RGpERAk11AJ98JIBcYjnYtWZwKBMZSMNUnkTx+ACgu4xY
4dw0KvVB2IMoopvaXerWT/k=
=rW6H
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-11-28 15:58 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
2007-11-28 14:36   ` Graeme Gregory
2007-11-28 15:55     ` Koen Kooi [this message]
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=474D8F63.6000401@student.utwente.nl \
    --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 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.