From: Will Deacon <will.deacon@arm.com>
To: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
Cc: Marc Zyngier <Marc.Zyngier@arm.com>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>,
Anup Patel <anup.patel@linaro.org>,
Patch Tracking <patches@linaro.org>,
Rusty Russell <rusty@rustcorp.com.au>,
"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>
Subject: Re: [RFC] arm64: Early printk support for virtio-mmio console devices.
Date: Fri, 19 Apr 2013 10:05:59 +0100 [thread overview]
Message-ID: <20130419090558.GA13283@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <CAAHg+HhtCorArCmx=ha0=64+SJZiizzrDUKSPLV=N+OzO8zAxQ@mail.gmail.com>
Hello,
On Thu, Apr 18, 2013 at 09:48:49AM +0100, Pranavkumar Sawargaonkar wrote:
> Actually i thought adding a config register will be easier to add a
> code than writing entire emulation as 8250 emulation will require to
> deal with dealing with more registers and more code.
kvmtool already has an 8250 emulation! All we need to do is hack together
something which will allow us to instantiate those ioport devices in a more
flexible manner (namely, inside the MMIO space for ARM). For earlyprintk, I
suspect we can get away without an interrupt too, which should simplify
things a bit to start with.
Regardless of the outcome of this discussion, I think getting the 8250
working on ARM is definitely something worth doing. If I get time, I'll take
a look.
Will
next prev parent reply other threads:[~2013-04-19 9:06 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 [this message]
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
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=20130419090558.GA13283@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Marc.Zyngier@arm.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