From: eddie.huang@mediatek.com (Eddie Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/5] ARM: dts: mt8135: enable basic SMP bringup for mt8135
Date: Wed, 11 Nov 2015 15:55:57 +0800 [thread overview]
Message-ID: <1447228557.20886.10.camel@mtksdaap41> (raw)
In-Reply-To: <7h1tbx1gjp.fsf@deeprootsystems.com>
Hi Kevin,
On Tue, 2015-11-10 at 17:16 -0800, Kevin Hilman wrote:
> Hi Eddie,
>
> [...]
>
> > I check the log [0],
>
> Thanks for checking into this boot failure.
>
> > it seems first time mt8135-evbp1 boot to kernel
> > shell successfully, then boot again. In the second time, mt8135 stay in
> > fastboot mode, waiting host send boot image, then timeout.
>
> Actually, it never gets to a shell the first time. If you look closely,
> the target reboots as soon as userspace starts. Look for the PYBOOT
> line which says "finished booting, starting userspace"
>
> Later on, pyboot thinks it finds a root shell due to finding '#'
> characters, but clearly it never got to a shell.
>
> > I download zImage and dtb in [1], and kernel run to shell successfully
> > on my platform.
>
> Are you can you try using a ramdisk as well? You can use the pre-built
> one here:
> http://storage.kernelci.org/images/rootfs/buildroot/armel/rootfs.cpio.gz
>
Yes, I tried this ramdisk, and I can reproduce fail issue.
> Please check my boot logs to see how I'm generating the boot.img file
> (search for mkbootimg) with a kernel/dtb/ramdisk. It may be possible
> that the kernel image size with a ramdisk is breaking some of the
> assumptions in the fastboot mode. I've seen problems like this on other
> platforms due to hard-coded sizes/addresses in the boot firmware.
>
MT8135 allocate 10MB for BOOT partition, but the test boot.img is 11MB,
thus cause user space fail. I will prepare new firmware that extend BOOT
partition to 16MB. and put new firmware on Howard's github. I will mail
to you when I am ready..
Eddie
Thanks
next prev parent reply other threads:[~2015-11-11 7:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 15:19 [PATCH v5 0/5] Add SMP bringup support for mt65xx socs Yingjoe Chen
2015-10-02 15:19 ` [PATCH v5 1/5] ARM: mediatek: enable gpt6 on boot up to make arch timer working Yingjoe Chen
2015-10-02 15:19 ` [PATCH v5 2/5] devicetree: bindings: add new SMP enable method Mediatek SoC Yingjoe Chen
2015-10-02 15:19 ` [PATCH v5 3/5] ARM: mediatek: add smp bringup code Yingjoe Chen
2015-10-02 15:19 ` [PATCH v5 4/5] ARM: dts: mt8135: enable basic SMP bringup for mt8135 Yingjoe Chen
2015-10-26 0:56 ` Kevin Hilman
2015-10-26 7:15 ` Yingjoe Chen
2015-10-26 8:06 ` Kevin Hilman
2015-10-26 11:40 ` Eddie Huang
2015-10-29 9:12 ` Kevin Hilman
2015-10-29 12:03 ` Eddie Huang
2015-11-09 17:59 ` Kevin Hilman
2015-11-10 6:11 ` Eddie Huang
2015-11-11 1:16 ` Kevin Hilman
2015-11-11 7:55 ` Eddie Huang [this message]
2015-11-11 23:50 ` Kevin Hilman
2015-11-12 4:54 ` Kevin Hilman
2015-11-12 12:46 ` Eddie Huang
2015-11-12 23:56 ` Kevin Hilman
2015-11-13 10:56 ` Eddie Huang
2015-10-02 15:19 ` [PATCH v5 5/5] ARM: dts: mt8127: enable basic SMP bringup for mt8127 Yingjoe Chen
2015-10-12 17:30 ` [PATCH v5 0/5] Add SMP bringup support for mt65xx socs Matthias Brugger
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=1447228557.20886.10.camel@mtksdaap41 \
--to=eddie.huang@mediatek.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).