From: Arun Reddy <reddyac@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for AT91RM9200EK?
Date: Sat, 19 Apr 2008 20:12:23 -0700 [thread overview]
Message-ID: <326f33790804192012obfa723aof17a9716b815012b@mail.gmail.com> (raw)
In-Reply-To: <844460.38324.qm@web31807.mail.mud.yahoo.com>
Hi Pink Boy,
While I am uncertain why uImage is not appearing in the source folder,
*"I'm wondering
is there is either an option I'm not setting, the current source
is broken and I need to use an older one, or there is some patch
I need."*
to solve the problem of retrieving the older source, cannot you simply
modify the .mk file and manually change the source file that is currently
listed to an older, available one?
Arun
On Sat, Apr 19, 2008 at 7:42 PM, Pink Boy <dasfoo@yahoo.com> wrote:
> Hi,
>
> One more thing, the command that seems to bomb,
>
>
> cp -pf
> /home/tu/workspace/arm920_tool/buildroot/project_build_arm/uclibc/linux-2.6.22.1/arch/arm/boot/uImage
>
> /home/tu/workspace/arm920_tool/buildroot/binaries/uclibc/at91rm9200ek-linux-2.6.22.1-20080420.gz
>
> The is no uImage in the source folder, there is however a zImage.
>
> ???
>
> Mr Foo
>
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20080419/ed74fbcc/attachment.htm
next prev parent reply other threads:[~2008-04-20 3:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 23:47 [Buildroot] r21760 and device_table.txt problems Christopher Taylor
2008-04-19 14:58 ` Hamish Moffatt
2008-04-20 2:10 ` [Buildroot] Buildroot for AT91RM9200EK? Pink Boy
2008-04-20 2:42 ` Pink Boy
2008-04-20 3:12 ` Arun Reddy [this message]
2008-04-24 0:07 ` Pink Boy
2008-04-24 14:57 ` Christopher Taylor
2008-04-24 15:27 ` Ulf Samuelsson
2008-04-20 5:17 ` [Buildroot] r21760 and device_table.txt problems Christopher Taylor
2008-04-21 14:06 ` Hamish Moffatt
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=326f33790804192012obfa723aof17a9716b815012b@mail.gmail.com \
--to=reddyac@gmail.com \
--cc=buildroot@busybox.net \
/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