mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	linaro-kernel@lists.linaro.org,
	Anup Patel <anup.patel@linaro.org>,
	patches@linaro.org, linux-kernel@vger.kernel.org,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] arm64: Early printk support for virtio-mmio console devices.
Date: Thu, 18 Apr 2013 12:01:32 +0200	[thread overview]
Message-ID: <20130418100132.GE4998@game.jcrosoft.org> (raw)
In-Reply-To: <CAAHg+HiHKV+8hBT1QWe4hSxocCX6wpRd3bCPWB7zU8jVFmPuAA@mail.gmail.com>

On 13:02 Thu 18 Apr     , Pranavkumar Sawargaonkar wrote:
> On 18 April 2013 12:21, Rusty Russell <rusty@rustcorp.com.au> wrote:
> >
> > PranavkumarSawargaonkar <pranavkumar@linaro.org> writes:
> > > From: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> > >
> > > This patch implements early printk support for virtio-mmio console devices without using any hypercalls.
> >
> > This makes some sense, though not sure that early console *read* makes
> > much sense.  I can see the PCI version of this being useful as well.
> 
> Read can be useful for "mach-virt" which will have only virtio console
> as a console device. Then if someone wants to have UEFI or any other
> boot-loader emulation, which expects user to input few things, in that
> case read might become handy.

yes I'm adding barebox on arm64 and will need it for virt target

Best Regards,
J.
> >
> >
> > The spec definition for this will be interesting, because it can be used
> > before the device is initialized (something which is generally
> > verboten).
> >
> > Cheers,
> > Rusty.
> 
> Thanks,
> Pranav
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2013-04-18 10:12 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
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 [this message]
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=20130418100132.GE4998@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=anup.patel@linaro.org \
    --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=pranavkumar@linaro.org \
    --cc=rusty@rustcorp.com.au \
    /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