From: Mauro Condarelli <mcondarelli@soft-in.com>
To: buildroot@busybox.net
Subject: [Buildroot] R: AT91SAM9G20 build .config for linux-2.6.26
Date: Mon, 29 Dec 2008 10:52:12 +0100 [thread overview]
Message-ID: <49589DCC.30909@soft-in.com> (raw)
In-Reply-To: <495891E7.2060908@panicking.kicks-ass.org>
michael ha scritto:
> Hi,
>
> Mauro Condarelli wrote:
>> Michael Trimarchi ha scritto:
>>> 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
>>>
>> Pretty please, I tried several (dozens of) configurations.
>> Can someone contribute a *surely working* .config file for my board?
>> I started "from the config file of 2.6.25 distribuition" (assuming You
>> mean the one that is available from www.kernel.org) multiple times,
>> never getting to a working kernel.
>>
>
> If you use the latest kernel you have the at91sam9g20ek_defconfig. The
> pathces for
> the at9samg20 are in the official kernel tree starting from the TAG
> v2.6.27-rc1
>
>> I really need to start from some "known good" point, otherwise I'm just
>> running circles.
>>
>> TiA
>> Mauro
>>
>
> The configs file are under arch/arm/configs/ directory of the kernel
> tree.
>
> Regards Michael
>
Hi,
Thanks.
I know that, unfortunately, for reasons independent of my will, I need
to stick to version 2.6.26.
Is there any *easy* way to backport the changes?
Can someone help me?
TiA
Mauro
next prev parent reply other threads:[~2008-12-29 9:52 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 ` [Buildroot] R: " Michael Trimarchi
2008-12-26 19:40 ` Mauro Condarelli
[not found] ` <495891E7.2060908@panicking.kicks-ass.org>
2008-12-29 9:52 ` Mauro Condarelli [this message]
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=49589DCC.30909@soft-in.com \
--to=mcondarelli@soft-in.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