From: Guenter Roeck <linux@roeck-us.net>
To: Michal Simek <michal.simek@xilinx.com>, Rob Herring <robh@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] scripts/dtc: Update to upstream version v1.6.0-51-g183df9e9c2b9
Date: Mon, 15 Feb 2021 08:15:06 -0800 [thread overview]
Message-ID: <06560f35-af85-5a75-80f5-9b2d44feec39@roeck-us.net> (raw)
In-Reply-To: <85d6deea-abd9-f7aa-8eb7-9067f6376d49@xilinx.com>
On 2/15/21 7:23 AM, Michal Simek wrote:
[ ... ]
>
>> I think the problem is here:
>>
>> /* initialize device tree for usage in early_printk */
>> early_init_devtree(_fdt_start);
>>
>> That probably also explains why enabling earlycon doesn't help.
>
> Can you please elaborate more on it?
> I see earlycon to be enabled quite early.
>
> [ 0.000000] Ramdisk addr 0x00000000,
> [ 0.000000] Compiled-in FDT at (ptrval)
Unless I was missing something, this is where it failed.
> [ 0.000000] earlycon: ns16550a0 at MMIO 0x44a01000 (options '115200n8')
> [ 0.000000] printk: bootconsole [ns16550a0] enabled
> [ 0.000000] cma: Reserved 16 MiB at 0xaec00000
>
[ ... ]
>
> Please send the patch. Would be the best as early as possible and I will
> queue it for 5.12.
>
https://lore.kernel.org/patchwork/patch/1380316/
Guenter
next prev parent reply other threads:[~2021-02-15 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 3:31 Guenter Roeck
2021-02-12 14:16 ` Rob Herring
2021-02-12 15:17 ` Guenter Roeck
2021-02-12 21:01 ` Rob Herring
2021-02-12 21:51 ` Guenter Roeck
2021-02-12 22:34 ` Rob Herring
2021-02-12 22:50 ` Guenter Roeck
2021-02-15 15:23 ` Michal Simek
2021-02-15 16:15 ` Guenter Roeck [this message]
2021-02-12 22:44 ` Guenter Roeck
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=06560f35-af85-5a75-80f5-9b2d44feec39@roeck-us.net \
--to=linux@roeck-us.net \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=robh@kernel.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
all inboxes | Powered by JetHome®