From: peter@hurleysoftware.com (Peter Hurley)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM, earlyconsole and io mapping
Date: Mon, 30 Mar 2015 19:31:42 -0400 [thread overview]
Message-ID: <5519DCDE.4010406@hurleysoftware.com> (raw)
In-Reply-To: <87iodivgfm.fsf@free.fr>
Hi Robert,
On 03/30/2015 08:05 AM, Robert Jarzmik wrote:
> Hi,
>
> I was wondering how the earlyconsole was supposed to work in order to add
> support to the pxa architecture. More specifically, I don't understand how the
> memory mapping is supposed to be available at the early parameters parsing.
>
> The thing I don't understand is that :
> - in kernel initialization, parse_early_param() is called before
> machine_desc->map_io()
> - as a consequence, the architecture didn't add the vm early mapping for serial
> peripheral (which is added in pxa_map_io())
> - as a consequence, earlycon_map() will fail to map the serial MMIO
> (as in stack showed in [1])
>
> Therefore, are there non-DT earlycon users on the list, and could they tell me
> what way they get earlycon support in their arm boards please ?
Fixmap support has not been upstreamed yet, but if you're desperate, here's
the latest patch version:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/318372.html
If you're using /chosen/stdout-path, earlycon gets turned off at dummy
VT console load, so for right now, specify your earlycon and consoles on the
command line.
Regards,
Peter Hurley
next prev parent reply other threads:[~2015-03-30 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 12:05 ARM, earlyconsole and io mapping Robert Jarzmik
2015-03-30 12:11 ` Thomas Petazzoni
2015-03-30 13:25 ` Robert Jarzmik
2015-03-30 23:31 ` Peter Hurley [this message]
2015-03-31 9:11 ` Robert Jarzmik
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=5519DCDE.4010406@hurleysoftware.com \
--to=peter@hurleysoftware.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).