From: "Pali Rohár" <pali.rohar@gmail.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Tony Lindgren <tony@atomide.com>,
Sebastian Reichel <sre@kernel.org>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
Pavel Machek <pavel@ucw.cz>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-kernel@lists.infradead.org,
Laura Abbott <lauraa@codeaurora.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: N900 v3.19-rc5 arm atags_to_fdt.c is broken
Date: Fri, 23 Jan 2015 22:39:55 +0100 [thread overview]
Message-ID: <201501232239.55801@pali> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 534 bytes --]
Hello,
when I boot zImage with appended DT n900 in qemu fdt_open_into()
function called from file arch/arm/boot/compressed/atags_to_fdt.c
(in function atags_to_fdt) always returns -FDT_ERR_NOSPACE.
It means that all ATAGS (including cmdline arguments) passed by
bootloader are ignored.
On real n900 device I see that booted DT version also ignore
cmdline arguments from bootloader. I cannot debug decompress code
on real device, but I think it is same problem as in qemu.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2015-01-23 21:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 21:39 Pali Rohár [this message]
2015-01-23 22:36 ` N900 v3.19-rc5 arm atags_to_fdt.c is broken Pali Rohár
2015-01-23 23:48 ` Pavel Machek
2015-01-24 9:04 ` Pali Rohár
2015-01-26 16:14 ` Tony Lindgren
2015-01-26 16:23 ` Pali Rohár
2015-01-26 17:03 ` Tony Lindgren
2015-01-26 18:57 ` Nicolas Pitre
2015-01-26 21:48 ` Pavel Machek
2015-01-27 0:06 ` Nicolas Pitre
2015-01-27 13:37 ` Pavel Machek
2015-01-27 15:16 ` Nicolas Pitre
2015-01-27 15:26 ` Pali Rohár
2015-01-27 15:26 ` Tony Lindgren
2015-01-27 17:53 ` Russell King - ARM Linux
2015-01-27 18:50 ` Nicolas Pitre
2015-01-27 23:09 ` Aaro Koskinen
2015-01-27 23:17 ` Pavel Machek
2015-02-02 13:39 ` Pavel Machek
2015-02-02 13:56 ` Nicolas Pitre
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=201501232239.55801@pali \
--to=pali.rohar@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pavel@ucw.cz \
--cc=santosh.shilimkar@ti.com \
--cc=sre@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 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).