From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX31 LogicPD LiteKit Kernel 2.6.33.2
Date: Thu, 15 Apr 2010 09:02:56 +0200 [thread overview]
Message-ID: <20100415070256.GJ30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <w2i3f34cd261004141302xdeb23378hfc4d795a6c9811c2@mail.gmail.com>
Hi,
On Wed, Apr 14, 2010 at 02:02:47PM -0600, Badguy Badguy wrote:
> I am attempting to boot the 2.6.33.2 Kernel on the LogicPD LiteKit iMX31.
> we have a board based on this one, and I am using it and the dev kit with no
> success.
>
> I see a lot of support in the mainline kernel for this board, is it safe to
> assume someone is able to boot this board using it?
Yes, that should work well. I've just recently used this board for
development.
> I am running the lolo bootloader from Logic, version 2.4.0.
>
> I have compiled the kernel using a fairly new ltib environment.
>
> Currently I run 2.6.19.2 from Freescale / Logic with success but now desire
> to upgrade the kernel to something with better MMC support, I am not stuck
> on 2.6.33.2 if someone can recommend a newer kernel that has some of the
> support I desire.
>
> When I attempt to boot the kernel, It hangs and this is my only output:
> Uncompressing Linux... done, booting the kernel.
>
> I have dug around a little bit as I get my feet wet in kernel
> initialization, and would appreciate any debug pointers or solutions or
> direction on how to solve this.
Could you set CONFIG_EARLY_PRINTK=y in your .config? If that doesn't
work, please post your config.
Thanks,
Daniel
next prev parent reply other threads:[~2010-04-15 7:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 20:02 iMX31 LogicPD LiteKit Kernel 2.6.33.2 Badguy Badguy
2010-04-15 7:02 ` Daniel Mack [this message]
2010-04-15 7:58 ` Daniel Mack
2010-04-15 21:08 ` Badguy Badguy
2010-04-16 8:36 ` Daniel Mack
2010-04-19 19:40 ` Badguy Badguy
2010-04-20 8:13 ` Daniel Mack
2010-04-21 22:35 ` Badguy Badguy
2010-04-21 22:47 ` Daniel Mack
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=20100415070256.GJ30801@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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.