From: Michael Trimarchi <trimarchimichael@yahoo.it>
To: buildroot@busybox.net
Subject: [Buildroot] R: AT91SAM9G20 build .config for linux-2.6.26
Date: Fri, 26 Dec 2008 19:24:12 +0000 (GMT) [thread overview]
Message-ID: <787962.90753.qm@web23507.mail.ird.yahoo.com> (raw)
In-Reply-To: <49552B28.5040203@soft-in.com>
Hi,
--- Ven 26/12/08, Mauro Condarelli <mcondarelli@soft-in.com> ha scritto:
> Da: Mauro Condarelli <mcondarelli@soft-in.com>
> Oggetto: [Buildroot] AT91SAM9G20 build .config for linux-2.6.26
> A: buildroot at uclibc.org
> Data: Venerd? 26 dicembre 2008, 20:06
> Hi,
> I've been trying to build the whole kernel+rootfs
> system for my
> AT91SAM9G20-EK Rev.B EVA board several times now and always
> failing, for
> one reason or the other.
>
> I tried both the straight instructions from
> buildroot.uclibc.org and
> those from www.linux4sam.org.
>
> I have a working set bootstrap+uboot+linux-2.6.25+rootfs
> BINARY ONLY!
>
> I am (for the time being) happy with the first two steps
> and I'm trying
> to setup a net boot with tftp+nfs.
> I have been able to set-up a server with working tftpd+nfsd
> that will
> boot the original stuff.
>
The rootfs is one thing. The kernel is another one. You can compile
the kernel outside the buildroot project using the same toolchain, start
from the config file of 2.6.25 distribuition.
Michael
next prev parent reply other threads:[~2008-12-26 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 19:06 [Buildroot] AT91SAM9G20 build .config for linux-2.6.26 Mauro Condarelli
2008-12-26 19:24 ` Michael Trimarchi [this message]
2008-12-26 19:40 ` [Buildroot] R: " Mauro Condarelli
[not found] ` <495891E7.2060908@panicking.kicks-ass.org>
2008-12-29 9:52 ` Mauro Condarelli
2008-12-29 10:01 ` Michael Trimarchi
2008-12-26 19:35 ` [Buildroot] " Bernhard Gödel
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=787962.90753.qm@web23507.mail.ird.yahoo.com \
--to=trimarchimichael@yahoo.it \
--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