linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mkl0301@gmail.com (Lin Mac)
To: linux-arm-kernel@lists.infradead.org
Subject: Booting CNS3420 EVB v 1.3 failed with 2.6.36 (and 2.6.35)
Date: Thu, 11 Nov 2010 09:55:05 +0800	[thread overview]
Message-ID: <AANLkTikt6aArfocc0aVfAXDczTmzURuwAit6GNRr8+PM@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikDEq=5ULX-sxaN95GaW9sQHX8qrCBwmcA6FD1E@mail.gmail.com>

2010/11/10 Lin Mac <mkl0301@gmail.com>:
> 2010/11/9 Russell King - ARM Linux <linux@arm.linux.org.uk>:
>> On Tue, Nov 09, 2010 at 01:14:33PM +0300, Anton Vorontsov wrote:
>>> On Tue, Nov 09, 2010 at 03:12:25PM +0800, Lin Mac wrote:
>>> > > setenv bootargs console=ttyS0,38400 ip=on
>>> > Changing this doesn't take effect. I was trying console=ttyS0,115200
>>> > and root=/dev/ram0, but it just boot with the configured parameter
>>> > instead of the given one.
>>> > Is it also the issue of u-boot?
>>> Nope. Just remove CONFIG_CMDLINE from your kernel .config file. ;-)
>> No. ?The external command line overrides the built-in one unless
>> CMDLINE_FORCE is set.
> I have confirmed that CONFIG_CMDLINE_FORCE is not set.
> Removing the CONFIG_CMDLINE caused linux boot fails:
It is fixed by enabling u-boot config CONFIG_CMDLINE_TAG,
CONFIG_SETUP_MEMORY_TAGS, CONFIG_MISC_INIT_R. Now it works just fine.
Thanks.

Best Regards,
Mac Lin

  reply	other threads:[~2010-11-11  1:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05  3:08 Booting CNS3420 EVB v 1.3 failed with 2.6.36 (and 2.6.35) Lin Mac
2010-11-05  7:44 ` Anton Vorontsov
2010-11-09  7:12   ` Lin Mac
2010-11-09 10:14     ` Anton Vorontsov
2010-11-09 10:35       ` Russell King - ARM Linux
2010-11-10  4:07         ` Lin Mac
2010-11-11  1:55           ` Lin Mac [this message]
2010-11-10  4:00       ` Lin Mac
2010-11-09  7:46 ` Lin Mac
2010-11-12 14:32 ` Russell King - ARM Linux
2010-11-14 21:58   ` Lin Mac

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=AANLkTikt6aArfocc0aVfAXDczTmzURuwAit6GNRr8+PM@mail.gmail.com \
    --to=mkl0301@gmail.com \
    --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).