All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for target PowerPC 405 (on Xilinx XUPV2p	Board)
Date: Wed, 10 Dec 2008 16:37:31 +0100	[thread overview]
Message-ID: <20081210153731.GC23100@mx.loc> (raw)
In-Reply-To: <10d6046f0812100657s396ae2a3n232aa92e681bde94@mail.gmail.com>

Please keep this on the mailing list, it may be helpful for others too.

On Wed, Dec 10, 2008 at 03:57:15PM +0100, Mirko ROCCO wrote:
>Ok, thanks, I realize that the problem was this... now buildroot seems to
>compile, but I have still a doubt: I'm using a kernel from Xilinx, with
>support for same IP core that i need for my board.
>
>So, can I use the .config file for Xilinx kernel even if it is not for a
>"native linux kernel"?

If the kernel is reasonable new then you can use that kernel and appropriate
.config, yes.

If you select Toolchain -> Kernel Headers -> Linux 2.6 snapshot then
a linux-2.6.tar.bz2 tarball is used which has to contain the kernel
sources in the "linux-2.6/" directory.

So, either you git clone git://kernel.org/.... linux-2.6
for an upstream kernel or you can
mv linux-kernel-2.6-from-vendor linux-2.6
# cd linux-2.6 && make mrproper
tar -cjf dl/linux-2.6.tar.bz2 linux-2.6
where "dl/" is the BR2_DL_DIR from your buildroot .config.

>
>Many thanks for any help,
>Mirko ROCCO
>
>
>2008/12/10 Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
>
>> On Wed, Dec 10, 2008 at 03:13:54PM +0100, Mirko ROCCO wrote:
>> >Hi! This is my config file for buildroot!
>>
>> BR2_KERNEL_none=y
>> # BR2_KERNEL_LINUX is not set
>>
>> You did not enable a kernel.
>> make menuconfig
>> goto the "kernel" and select "Kernel type" linux.
>> Enable "linux kernel" and set ".config file" to the
>> kernel config you want to use (e.g. "br2.ppc-405-kernel.config").
>> If you do not yet have a kernel .config file prepared, then you
>> can copy one of the ppc defconfig to that very file to the toplevel
>> directory.
>>
>> HTH,
>>
>> >
>> >Mirko ROCCO
>> >
>> >
>> >2008/12/10 Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
>> >
>> >> On Wed, Dec 10, 2008 at 02:07:56PM +0100, Mirko ROCCO wrote:
>> >> >Hi Bernhard!
>> >> >I try to use your tree as you suggest me!
>> >> >
>> >> >Unfortunately I recive this error and i don't know how to solve it:
>> >>
>> >> Please show me your buildroot (toplevel) .config
>> >>
>>
>>
>>

      parent reply	other threads:[~2008-12-10 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 15:40 [Buildroot] Buildroot for target PowerPC 405 (on Xilinx XUPV2p Board) Mirko ROCCO
2008-12-01 16:10 ` Bernhard Reutner-Fischer
2008-12-02 12:04   ` Mirko ROCCO
2008-12-10 13:07   ` Mirko ROCCO
2008-12-10 14:00     ` Bernhard Reutner-Fischer
     [not found]       ` <10d6046f0812100613m2f54f43cx4c4c413dbea7df25@mail.gmail.com>
2008-12-10 14:44         ` Bernhard Reutner-Fischer
     [not found]           ` <10d6046f0812100657s396ae2a3n232aa92e681bde94@mail.gmail.com>
2008-12-10 15:37             ` Bernhard Reutner-Fischer [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=20081210153731.GC23100@mx.loc \
    --to=rep.dot.nop@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 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.