From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel version
Date: Tue, 25 Sep 2012 10:17:01 +0200 [thread overview]
Message-ID: <5061687D.8090703@mind.be> (raw)
In-Reply-To: <1348558164.41699.YahooMailNeo@web164601.mail.gq1.yahoo.com>
On 09/25/12 09:29, Zoran Djordjevic wrote:
> I will try to be more specific and I am aware that host kernel version doesn't matter in this story.
> I have kernel sources for my board 2.6.32 on let' say "BoardKernelDir" directy. There, I also have ".config" file, for
> kernel configuration.
> Then I go into Buildroot menues (make menuconfig) and under "Kernel/Kernel version"
> choose 3.2.6. In that same page of Buildroot menu, I can choose "Kernel configuration (Using custom configuration file)"
> to be the one I mentioned above (".config").
> Question is - is it wrong procedure and what kernel will be built this way- the one from
> "BoardKernelDir" (2.6.32) or 3.2.6 or (probably) it will make some mess ?
This will work, more or less. It will download the 3.2.6 kernel and run its
configure with your 2.6.32 .config. That will give you a lot of questions on
the console about config options which exist in the 3.2.6 kernel but didn't
exist yet in the 2.6.32 kernel. So not necessarily the most efficient
approach.
> Also, can I somehow (in Buildroot) use sources for my board - not those downloaded from kernel.org.
> I intend to use CrosstoolNG.
Yes you can: use the "custom tarball" option that I mentioned in my mail.
You have to configure that separately for buildroot and for crosstool-NG.
AFAIK buildroot doesn't allow to give a directory, so you'll have to make
a tarball from the directory first.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-09-25 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 20:11 [Buildroot] Kernel version Zoran Djordjevic
2012-09-24 21:24 ` Arnout Vandecappelle
2012-09-25 7:29 ` Zoran Djordjevic
2012-09-25 8:17 ` Arnout Vandecappelle [this message]
2012-09-25 11:57 ` Zoran Djordjevic
2012-09-25 13:48 ` Arnout Vandecappelle
2012-09-25 8:24 ` Stephan Hoffmann
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=5061687D.8090703@mind.be \
--to=arnout@mind.be \
--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