LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: bennett78@lpbroadband.net
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kernel@avr32linux.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] AVR32 fixes
Date: Tue, 26 Jun 2007 09:02:22 +0200 [thread overview]
Message-ID: <20070626090222.2f4abe6e@dhcp-255-175.norway.atmel.com> (raw)
In-Reply-To: <46802222.90104@lpbroadband.net>
On Mon, 25 Jun 2007 14:14:26 -0600
Frank Bennett <bennett78@lpbroadband.net> wrote:
> makes fine, but requires :
Hmm...what do you mean?
> export ARCH=avr32
> export CROSS_COMPILE=avr32-linux-
Standard cross-compile stuff.
> make defconfig
> make
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> CHK include/linux/compile.h
> MODPOST vmlinux
> UIMAGE arch/avr32/boot/images/uImage
> "mkimage" command not found - U-Boot images will not be built
Seems like you don't have mkimage installed. You can find it under
"tools" in the u-boot sources.
> Image arch/avr32/boot/images/uImage is ready
> make[1]: `arch/avr32/boot/images/vmlinux.elf' is up to date.
> Building modules, stage 2.
> MODPOST 20 modules
I'm sorry, but I don't understand what's wrong here...
Haavard
next prev parent reply other threads:[~2007-06-26 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 14:41 Haavard Skinnemoen
2007-06-25 20:14 ` Frank Bennett
2007-06-26 7:02 ` Haavard Skinnemoen [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-18 15:38 Haavard Skinnemoen
2008-05-27 8:17 [GIT PULL] avr32 fixes Haavard Skinnemoen
2008-02-29 13:46 Haavard Skinnemoen
2007-06-14 17:00 [GIT PULL] AVR32 fixes Haavard Skinnemoen
2007-03-07 10:10 Haavard Skinnemoen
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=20070626090222.2f4abe6e@dhcp-255-175.norway.atmel.com \
--to=hskinnemoen@atmel.com \
--cc=bennett78@lpbroadband.net \
--cc=kernel@avr32linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--subject='Re: [GIT PULL] AVR32 fixes' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).