linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: add fixmap based earlycon support
Date: Tue, 2 Jun 2015 01:25:15 +0100	[thread overview]
Message-ID: <20150602002514.GV2067@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAL_JsqK1fbd0p57iB996uZB6cFS4J5o0ieRs0pStseEb__FJ0w@mail.gmail.com>

On Mon, Jun 01, 2015 at 06:57:24PM -0500, Rob Herring wrote:
> On Mon, Jun 1, 2015 at 6:31 PM, Russell King - ARM Linux
> <linux@arm.linux.org.uk> wrote:
> >> > DT based earlycon is a *really* useful thing to have if you are
> >> > working on early kernel code.
> >> > With many of the DTs now having been extended with a
> >> > /chosen/stdout-path property, it really only takes a simple 'earlycon'
> >> > command line parameter (without any arguments) to get console output
> >> > as soon as the early DT scan is concluded. I suppose this is also a
> >> > useful thing for multi platform kernels?
> >>
> >> Certainly, that's the whole point. IMO, we should rip out most of
> >> DEBUG_LL when this is merged.
> >
> > If you think that, you're wrong.  DEBUG_LL exists to be able to debug
> > stuff well before the kernel gets anywhere near the C code.  It has
> > to stay.  It fills the gap where no C code can do any debugging.
> 
> Right, that is the part we should keep. However, we won't really need
> earlyprintk (which I recall you are no fan of) and we don't need all
> the kconfig of addresses which is getting quite unwieldy.

Both points are true, but we definitely want to keep the information
concerning where the uarts are.  I certainly don't want to go hunting
in old paper documentation for some of that information... maybe
moving it into Documentation/arm somewhere would make sense -
possibly in a set of per-vendor files or maybe a single file separated
by vendor or something like that to break it up from being one huge
conflict-ridden list.

-- 
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2015-06-02  0:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 13:51 [RFC PATCH] ARM: add fixmap based earlycon support Ard Biesheuvel
2015-05-01 16:18 ` Russell King - ARM Linux
2015-05-02  8:37   ` Ard Biesheuvel
2015-06-01  8:26     ` Ard Biesheuvel
2015-06-01 11:00       ` Stefan Agner
2015-06-01 23:26       ` Rob Herring
2015-06-01 23:31         ` Russell King - ARM Linux
2015-06-01 23:57           ` Rob Herring
2015-06-02  0:25             ` Russell King - ARM Linux [this message]
2015-06-02  6:32           ` Ard Biesheuvel

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=20150602002514.GV2067@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).