From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel does not boot on I.MX28
Date: Fri, 13 Apr 2012 09:56:17 +0200 [thread overview]
Message-ID: <20120413095617.0b583ec8@skate> (raw)
In-Reply-To: <63D6870D443E63419AC4A0C97B86C0920D358F816B@MBXCLUSTER.mdh.local>
Le Fri, 13 Apr 2012 09:38:58 +0200,
Mikael ?sberg <mikael.asberg@mdh.se> a ?crit :
> First I did 'make menuconfig' and set mxs_defconfig, and then 'make'.
> Then I do 'make linux-menuconfig' (adding as many UART options as possible).
> I do a 'make menuconfig' again and set Kernel --> Kernel configuration --> Using a custom config file.
> I change file path to output/build/linux-3.2.6/.config (instead of mxs_defconfig).
You don't need to do this last step. 'make linux-menuconfig' will edit
the output/build/linux-3.2.6/.config file, and it will be use at the
next invocation of make.
However, you will want to save your .config file somewhere else in
order to not lose it when you'll do a make clean.
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
Build your kernel with CONFIG_EARLYPRINTK and pass the "earlyprintk"
argument on the kernel command line. It will give some more details on
what's happening.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-04-13 7:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 7:38 [Buildroot] Kernel does not boot on I.MX28 Mikael Åsberg
2012-04-13 7:56 ` Attila Kinali
2012-04-13 8:21 ` Mikael Åsberg
2012-04-13 8:31 ` Attila Kinali
2012-04-13 9:06 ` Mikael Åsberg
2012-04-13 9:23 ` Thomas Petazzoni
2012-04-13 9:53 ` Mikael Åsberg
2012-04-13 7:56 ` Thomas Petazzoni [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=20120413095617.0b583ec8@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