mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Will Deacon <Will.Deacon@arm.com>,
	"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
	Patch Tracking <patches@linaro.org>,
	Marc Zyngier <Marc.Zyngier@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Subject: Re: [RFC] arm64: Early printk support for virtio-mmio console devices.
Date: Fri, 19 Apr 2013 17:22:26 +0100	[thread overview]
Message-ID: <20130419162226.GB5383@localhost.cambridge.arm.com> (raw)
In-Reply-To: <CAFEAcA-F18kR4JihdxaLTm3qb4n51tsygG1RW4djwJ0u9+FQqw@mail.gmail.com>

On Fri, Apr 19, 2013 at 05:14:36PM +0100, Peter Maydell wrote:
> On 19 April 2013 17:12, Catalin Marinas <catalin.marinas@arm.com> wrote:
> > On Fri, Apr 19, 2013 at 11:05:47AM +0100, Peter Maydell wrote:
> >> Please make the kernel pick the device out of the device tree
> >> blob. The whole point of device tree is that it's how to tell
> >> the kernel where things live -- making kvmtool/QEMU and/or the
> >> user also have to mess with the kernel command line is awkward
> >> and annoying.
> >
> > For a normal console device, it indeed needs to get it from the DT. For
> > early console, you want it earlier than DT parsing so we pass it on the
> > kernel command line via the earlyprintk= parameter.
> 
> You should fix your DT handling code so you can get at the info
> when you need it rather than pushing the problem into bootloaders
> and QEMU, please. DT is your data structure so feel free to
> (re)design it so relevant information can be accessed early
> if that's useful.

earlyprintk is used for debugging early problems, like DT parsing. You
don't have to use it unless you are debugging something. Without
earlyprintk you just get a normal console during boot, based on the DT
description.

-- 
Catalin

  reply	other threads:[~2013-04-19 16:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-18  5:52 PranavkumarSawargaonkar
2013-04-18  6:49 ` Marc Zyngier
2013-04-18  7:24   ` Pranavkumar Sawargaonkar
     [not found]   ` <CAAHg+HhajHFC=1nh6YQNgpf=Na2FqcsYJ=t+ag9QiTg6TxUz9w@mail.gmail.com>
2013-04-18  7:36     ` Marc Zyngier
2013-04-18  8:48       ` Pranavkumar Sawargaonkar
2013-04-18  8:53         ` Alexander Graf
2013-04-19  9:05         ` Will Deacon
2013-04-19  9:25           ` Pranavkumar Sawargaonkar
2013-04-19  9:27             ` Will Deacon
2013-04-19  9:30               ` Peter Maydell
2013-04-19  9:34                 ` Pranavkumar Sawargaonkar
2013-04-19  9:39                   ` Will Deacon
2013-04-19 10:05                     ` Peter Maydell
2013-04-19 16:12                       ` Catalin Marinas
2013-04-19 16:14                         ` Peter Maydell
2013-04-19 16:22                           ` Catalin Marinas [this message]
2013-04-19 16:33                             ` Peter Maydell
2013-04-19 17:14                               ` Catalin Marinas
2013-04-19 17:40                                 ` Peter Maydell
2013-04-19  9:36                 ` Will Deacon
2013-04-18 19:06       ` Pranavkumar Sawargaonkar
2013-04-18  8:30   ` Peter Maydell
2013-04-18  8:51     ` Alexander Graf
2013-04-18  8:51     ` Marc Zyngier
2013-04-18  6:51 ` Rusty Russell
2013-04-18  7:32   ` Pranavkumar Sawargaonkar
2013-04-18  8:44     ` Alexander Graf
2013-04-18  8:55       ` Pranavkumar Sawargaonkar
2013-04-18 10:01     ` Jean-Christophe PLAGNIOL-VILLARD
2013-04-22  1:21     ` Rusty Russell
2013-04-22  3:10       ` Anup Patel
2013-04-22  5:15         ` Rusty Russell
2013-04-23  5:53           ` Pranavkumar Sawargaonkar
2013-04-22 14:50         ` Alexander Graf
2013-04-18 15:25 ` Christopher Covington
2013-04-18 15:59   ` Marc Zyngier
2013-04-18 18:59     ` Pranavkumar Sawargaonkar

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=20130419162226.GB5383@localhost.cambridge.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=Will.Deacon@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=pranavkumar@linaro.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

Powered by JetHome