From: Kyle McMartin <kmcmarti@redhat.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: 3.11-rc1+ multiplatform kernel+dtb pandaboard issues
Date: Thu, 22 Aug 2013 10:00:34 -0400 [thread overview]
Message-ID: <20130822140034.GL26531@redacted.bos.redhat.com> (raw)
In-Reply-To: <20130822063449.GO7656@atomide.com>
On Wed, Aug 21, 2013 at 11:34:50PM -0700, Tony Lindgren wrote:
> * Kyle McMartin <kmcmarti@redhat.com> [130821 12:48]:
> > On Wed, Aug 21, 2013 at 11:43:21AM -0400, Kyle McMartin wrote:
> > > I've suspected there might be a config issue, as omap2_defconfig
> > > works alright, as does booting a uImage with an appended
> > > omap4-panda.dtb, but there's no love with a zImage + initrd + dtb
> > > (or even just zImage without initrd + dtb.)
> > >
> >
> > after some further investigation, something odd is going on... turns
> > out things have been working (at least until initrd time, but that's
> > another story) fine but none of the bootargs have made it into the
> > kernel, so console= was unset and no messages came out.
>
> Hmm I've seen that with extra quotes around the u-boot bootargs line.
> But if things work OK with omap2plus_defconfig, then it sounds that
> something gets trashed with your .config options. Care to post your
> .config file somewhere?
>
Sure, CONFIG_CMDLINE is "" for us...
http://kyle.fedorapeople.org/config-3.11.0-0.rc6.git0.1.fc20.armv7hl
--Kyle
next prev parent reply other threads:[~2013-08-22 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 15:43 3.11-rc1+ multiplatform kernel+dtb pandaboard issues Kyle McMartin
2013-08-21 19:41 ` Kyle McMartin
2013-08-22 0:25 ` Sebastian Reichel
2013-08-22 17:19 ` Kyle McMartin
2013-08-22 6:34 ` Tony Lindgren
2013-08-22 14:00 ` Kyle McMartin [this message]
2013-08-26 14:20 ` Tony Lindgren
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=20130822140034.GL26531@redacted.bos.redhat.com \
--to=kmcmarti@redhat.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.