From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: vexpress: Remove non-DT code
Date: Wed, 17 Sep 2014 17:11:01 +0100 [thread overview]
Message-ID: <1410970261.30394.15.camel@hornet> (raw)
In-Reply-To: <20140917152735.GU12361@n2100.arm.linux.org.uk>
On Wed, 2014-09-17 at 16:27 +0100, Russell King - ARM Linux wrote:
> On Wed, Sep 10, 2014 at 04:40:57PM +0100, Pawel Moll wrote:
> > On Wed, 2014-09-10 at 15:58 +0100, Russell King - ARM Linux wrote:
> > > So, I'll then be asking ARM to provide updated instructions on how to
> > > boot the CT9x4 with DT...
>
> Let me repeat: a boot loader with network booting capability is an
> absolute necessity for me. This is *required* for unattended boots of
> kernels which have just been built. If a platform doesn't have this
> capability, I'm just not interested in it, and I _will_ not use it. It
> really is that simple.
>
> My position on the boot loader issue is not going to change; it's a
> fundamental requirement for automatic build and boot testing, and for
> efficient workflow at other times.
I understand.
As Boot Monitor is not going to do TFTP in foreseeable future, the
"compat" approach of glueing zImage with dtb is a potential solution.
I've just tested a build with CONFIG_ARM_ATAG_DTB_COMPAT=y and
CONFIG_ARM_ATAG_DTB_COMPAT_CMDLINE_FROM_BOOTLOADER=y - after cat-ing
arch/arm/boot/zImage with arch/arm/boot/dts/vexpress-v2p-ca9.dtb
everything worked fine, booting with a root filesystem on a MMC card.
Of course I tried this with Boot Monitor, but I would hope that it will
work with uboot without any problem as well.
Pawel
next prev parent reply other threads:[~2014-09-17 16:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 14:33 [PATCH 1/2] ARM: vexpress: Add CLCD Device Tree properties Pawel Moll
2014-09-10 14:33 ` [PATCH 2/2] ARM: vexpress: Remove non-DT code Pawel Moll
2014-09-10 14:58 ` Russell King - ARM Linux
2014-09-10 15:40 ` Pawel Moll
2014-09-17 15:27 ` Russell King - ARM Linux
2014-09-17 16:11 ` Pawel Moll [this message]
2014-09-18 1:04 ` Nicolas Pitre
2014-09-18 7:57 ` Russell King - ARM Linux
2014-09-18 9:19 ` Pawel Moll
2014-09-18 17:17 ` Nicolas Pitre
2014-09-10 17:45 ` Mike Turquette
2014-09-16 23:30 ` Lee Jones
2014-09-17 14:59 ` Pawel Moll
2014-09-17 15:42 ` Lee Jones
2014-09-17 15:46 ` Pawel Moll
2014-09-17 16:54 ` Lee Jones
2014-09-17 16:43 ` [PATCH v2] " Pawel Moll
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=1410970261.30394.15.camel@hornet \
--to=pawel.moll@arm.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 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.