Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Image created is not booting, waiting for infinite time
Date: Sun, 29 Jan 2012 12:44:34 +0100	[thread overview]
Message-ID: <20120129124434.3096460b@skate> (raw)
In-Reply-To: <BLU0-SMTP3763BD6AB472CBE81E9839DD28C0@phx.gbl>

Le Sun, 29 Jan 2012 17:12:57 +0530,
inblueswithu <inblueswithu@hotmail.com> a ?crit :

> The kernel headers version I used is 2.6.37.x. So my kernel on the 
> target will be of that version.

Your conclusion is wrong: it is not because you have used the kernel
headers 2.6.37.x that you *must* use 2.6.37 on your target.

Please read carefully:

 The kernel headers version *CAN* be different from the kernel version
 running on the target, as long as the kernel headers version is
 *OLDER* than the kernel version running on the target.

> But the kernel configuration is given as linux-3.1.config
> So, my doubt is, will this new config file which indicates to be for 
> kernel 3.1.x version
> work fine with 2.6.37.x version of kernel?

It might require some minor adaptation.

But still, I don't understand your persistence in trying to use 2.6.37
while the qemu_arm_versatile_defconfig is a known working
configuration. Can you please try with that one without any
modification.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-01-29 11:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28  8:25 [Buildroot] Image created is not booting, waiting for infinite time inblueswithu
2012-01-28 11:49 ` Thomas Petazzoni
2012-01-29  6:30   ` inblueswithu
2012-01-29  9:36     ` Thomas Petazzoni
2012-01-29 11:42       ` inblueswithu
2012-01-29 11:44         ` Thomas Petazzoni [this message]
2012-01-29 12:05           ` inblueswithu
2012-01-30  8:11           ` inblueswithu
2012-01-28 12:24 ` Samuel Martin

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=20120129124434.3096460b@skate \
    --to=thomas.petazzoni@free-electrons.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