From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM, earlyconsole and io mapping
Date: Mon, 30 Mar 2015 15:25:07 +0200 [thread overview]
Message-ID: <87bnjavcr0.fsf@free.fr> (raw)
In-Reply-To: <20150330141148.299f38a4@free-electrons.com> (Thomas Petazzoni's message of "Mon, 30 Mar 2015 14:11:48 +0200")
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Dear Robert Jarzmik,
>
> On Mon, 30 Mar 2015 14:05:33 +0200, Robert Jarzmik wrote:
> A very early mapping of the I/O space is done in head.S, way before you
> get into C code:
>
> http://lxr.free-electrons.com/source/arch/arm/kernel/head.S#L277
That's DEBUG_LL, right ? If that's what you mean, then I already have DEBUG_LL,
but that doesn't answer my question, as DEBUG_LL stops spitting logs after the
decompressor, and the errors I want to trap are between end of decompressor and
drivers probe.
And my question about earlycon remains, DEBUG_LL is not earlycon.
Cheers.
--
Robert
next prev parent reply other threads:[~2015-03-30 13:25 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 [this message]
2015-03-30 23:31 ` Peter Hurley
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=87bnjavcr0.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).