From: rosysong at rosinson.com <rosysong@rosinson.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Kernel hang when replace older uboot with uboot master V2
Date: Wed, 20 Feb 2019 10:16:51 +0800 [thread overview]
Message-ID: <201902201016506560860@rosinson.com> (raw)
In-Reply-To: 20190219114903.66ed8250@jawa
My old u-boot is 1.1.4
On Tue, 19 Feb 2019 17:45:12 +0800
"rosysong at rosinson.com" <rosysong@rosinson.com> wrote:
> Thanks for your reply, but this firmware can find the rootfs itself,
>
> >[ 0.337492] 5 fixed-partitions partitions found on MTD device
> >spi0.0 [ 0.344060] Creating 5 MTD partitions on "spi0.0":
> >[ 0.349014] 0x000000000000-0x000000040000 : "u-boot"
> >[ 0.354834] 0x000000040000-0x000000050000 : "u-boot-env"
> >[ 0.360944] 0x000000050000-0x000000060000 : "factory"
> >[ 0.366831] 0x000000060000-0x000000fe0000 : "firmware"
> >[ 0.374973] 2 uimage-fw partitions found on MTD device firmware
> >[ 0.381090] Creating 2 MTD partitions on "firmware":
> >[ 0.386258] 0x000000000000-0x000000190000 : "kernel"
> >[ 0.392027] 0x000000190000-0x000000f80000 : "rootfs"
> >[ 0.397783] mtd: device 5 (rootfs) set to be root filesystem
>
This is too late - as this is the MTD partition info provided from
kernel's DTB.
You need the root= information which is probably available on your
environment (not accessible by some reason from new u-boot).
BTW: What is the version of old u-boot ?
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
next prev parent reply other threads:[~2019-02-20 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:30 [U-Boot] Kernel hang when replace older uboot with uboot master V2 rosysong at rosinson.com
2019-02-19 9:37 ` Lukasz Majewski
2019-02-19 9:45 ` rosysong at rosinson.com
2019-02-19 10:49 ` Lukasz Majewski
2019-02-20 2:16 ` rosysong at rosinson.com [this message]
2019-02-19 9:48 ` rosysong at rosinson.com
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=201902201016506560860@rosinson.com \
--to=rosysong@rosinson.com \
--cc=u-boot@lists.denx.de \
/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