From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] KVM/arm: kernel low level debug support for ARM32 virtual platforms
Date: Tue, 3 Nov 2015 17:33:44 +0000 [thread overview]
Message-ID: <20151103173344.GC8644@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <5638E1CD.8090006@codeaurora.org>
On Tue, Nov 03, 2015 at 11:33:17AM -0500, Christopher Covington wrote:
> > diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
> > index a2e16f9..d126bd4 100644
> > --- a/arch/arm/Kconfig.debug
> > +++ b/arch/arm/Kconfig.debug
> > @@ -1155,6 +1155,28 @@ choice
> > This option selects UART0 on VIA/Wondermedia System-on-a-chip
> > devices, including VT8500, WM8505, WM8650 and WM8850.
> >
> > + config DEBUG_VIRT_UART_QEMU
> > + bool "Kernel low-level debugging on QEMU Virtual Platform"
> > + depends on ARCH_VIRT
> > + select DEBUG_UART_PL01X
> > + help
> > + Say Y here if you want the debug print routines to direct
> > + their output to PL011 UART port on QEMU Virtual Platform.
> > + Appropriate address values are:
> > + PHYS VIRT
> > + 0x9000000 0xf8090000
>
> I thought the only guarantee the virt machine had about the memory map was
> that it would be described in the device tree.
This LL debug stuff is used prior to device tree being parsed.
--
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-11-03 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 23:51 [PATCH] KVM/arm: kernel low level debug support for ARM32 virtual platforms Mario Smarduch
2015-11-03 16:33 ` Christopher Covington
2015-11-03 17:33 ` Russell King - ARM Linux [this message]
2015-11-03 17:44 ` Mario Smarduch
2015-11-03 17:55 ` Will Deacon
2015-11-03 19:17 ` Mario Smarduch
2015-11-03 19:39 ` Rob Herring
2015-11-04 13:31 ` Christoffer Dall
2015-11-04 18:49 ` Christopher Covington
2015-11-04 18:51 ` Ard Biesheuvel
2015-11-04 23:28 ` Mario Smarduch
2015-11-05 1:13 ` Peter Hurley
2015-11-05 15:04 ` Christoffer Dall
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=20151103173344.GC8644@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).