From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM, earlyconsole and io mapping
Date: Tue, 31 Mar 2015 11:11:09 +0200 [thread overview]
Message-ID: <874mp1v8eq.fsf@free.fr> (raw)
In-Reply-To: <5519DCDE.4010406@hurleysoftware.com> (Peter Hurley's message of "Mon, 30 Mar 2015 19:31:42 -0400")
Peter Hurley <peter@hurleysoftware.com> writes:
> 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.
> 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
Ah I'm not desperate, that would be nice to have tool on my automation
platform. I've gone the DEBUG_LL + JTAG/__log_buf memory dump so far.
And yet I remember viewing early concole patches a few monthes back, and I
wondered how the authors could make them work ... And as my memory didn't serve
me well, I couldn't remember your name.
> 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.
Ah I'm using device-tree in only 1/3rd of the PXA tests :
- 1/3rd for legacy platform_data tests
- 1/3rd for device-tree pxa platforms
- 1/3rd for multiplatform kernel
Anyway, I hope you'll have Russell's comments addressed, and that your patch
will make it upstream. Thanks for the information, it is exactly what I was
asking for.
Cheers.
--
Robert
prev parent reply other threads:[~2015-03-31 9:11 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
2015-03-31 9:11 ` Robert Jarzmik [this message]
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=874mp1v8eq.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--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).