From: daniel@caiaq.de (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: iMX31 LogicPD LiteKit Kernel 2.6.33.2
Date: Tue, 20 Apr 2010 10:13:23 +0200 [thread overview]
Message-ID: <20100420081323.GD30807@buzzloop.caiaq.de> (raw)
In-Reply-To: <z2z3f34cd261004191240nce56a951jb24c4ce3c0c47503@mail.gmail.com>
On Mon, Apr 19, 2010 at 01:40:50PM -0600, Badguy Badguy wrote:
> Ok, well I think my problem was simply that I did not have the console
> enabled! Oops!
> and once I seen the LED light go solid, I figured it was locked.
> (must not be being turned off)
>
> I will mention that the serial port defaults to the 9600 baud implied
> by the driver, this was also giving me trouble.
> I note it attempts to read current state and use it, but must get it
> wrong have not dug deeper yet, simply changed default to what the
> bootloader is using 115200
Yes, you should pass that on the kernel command line.
> I cleaned up my config some more, removed some redundant stuff got it
> to boot to Oops from lack of FS support.
> cannot get to the NFS server, digging into that.
Proably also some config issue? Works well here.
> Can I get a break down on how far you have run this kernel? Do you
> have file system support?
I can fully boot the board via NFS and have a working system with
Ethernet, MMC/SDIO, LED, GPIO, SPI and USB support.
> I notice the NAND driver is throwing bad erase block warnings on a
> large number of blocks, I will change SOM and see if it continues.
I'll again check for NAND and NOR later today, but I'm sure the chips
are at least probed correctly.
Daniel
next prev parent reply other threads:[~2010-04-20 8:13 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
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 [this message]
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=20100420081323.GD30807@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).