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: Solution for AVR32 kernel link problem
Date: Mon, 04 Feb 2008 13:14:13 +0100	[thread overview]
Message-ID: <47A70195.5060205@student.utwente.nl> (raw)
In-Reply-To: <47A3720F.1060303@miromico.ch>

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

Alex schreef:
| Hi
|
| I played around with OE for AVR32.
|
| I think I found a solution for the kernel linking problem.

<snip>

Great catch! This also fixes the build of alsa, it is applied in OE now.

|
| Finally, I couldn't test it, as I can't boot the kernel. Something is
| wrong with my load address and entry point. It is set to 0x20008000. I
| tried to
| add UBOOT_ENTRYPOINT = "90000000" to atngw100.conf and just recompile
| the kernel by "bitbake virtual/kernel -c clean" and "bitbake
| virtual/kernel".
| This didn't change the entry point, but maybe I have to recompile
| everything..

For my ngw with uboot from git (3 week old) the following works:

mkimage -A avr32 -O linux -T kernel -C none -a 0x10000000 -e 0x90000000
- -n 'koen 24rcgit' -d arch/avr32/boot/images/vmlinux.bin uImage

I changed linux.inc and atngw100.conf to allow the loadadress to be
different from the entry point.

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)

iD8DBQFHpwGVMkyGM64RGpERAtxkAKCnqnup+rV12sisqk8oMO7hkxYfogCdGTFG
zlIWKrqpDk8Tx8kQeoCvzE4=
=eIAw
-----END PGP SIGNATURE-----



      reply	other threads:[~2008-02-04 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-01 19:25 Solution for AVR32 kernel link problem Alex
2008-02-04 12:14 ` 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=47A70195.5060205@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.