linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel 3.4 on Dreamplug: no serial console
Date: Sat, 02 Jun 2012 16:18:09 +0100	[thread overview]
Message-ID: <3643648.ul01ikopg8@gromit> (raw)
In-Reply-To: <loom.20120602T135715-548@post.gmane.org>

On Saturday 02 Jun 2012 12:20:59 Hans Kr?ner wrote:
> Hello,
> 
> I built a 3.4 kernel by grabbing the sources off kernel.org at
> /pub/linux/kernel/v3.0/linux-3.4.tar.bz2
> 
> I built both the uImage with FDT support for the Dreamplug and it's
> respective dtb, and placed them on the Dreamplug's internal SD. I made
> minor tweaks to my U-boot env to handle FDT and proceeded to boot.
> 
> At first I thought the Dreamplug was hanging while booting the kernel, since
> the console hangs at "Uncompressing Linux... done, booting the kernel."
> However, doing the "post mortem" analysis and using U-boot to look at
> __log_buf, I could see the kernel actually booting fine. I let it boot and
> then SSHd into the box, everything seems fine.

your .config doesn't seem to be attached but this sounds similiar to the 
problem I had when converting a kernel config to FDT because I didn't have

CONFIG_SERIAL_OF_PLATFORM=y

which is needed to support configuring serial ports with FDT

Hope that Helps

Adam

  reply	other threads:[~2012-06-02 15:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02 12:20 Kernel 3.4 on Dreamplug: no serial console Hans Kröner
2012-06-02 15:18 ` Adam Baker [this message]
2012-06-03 15:26 ` Hans Kröner
2012-06-03 16:59   ` Adam Baker
2012-06-03 17:12     ` Arnd Bergmann
2012-06-03 18:40       ` Jason Cooper
2012-06-03 19:09         ` Andrew Lunn
2012-06-04  8:29         ` Florian Fainelli
2012-06-04 14:30           ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2012-06-02 18:57 Andrew Lunn

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=3643648.ul01ikopg8@gromit \
    --to=linux@baker-net.org.uk \
    --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).