From mboxrd@z Thu Jan 1 00:00:00 1970 From: cov@codeaurora.org (Christopher Covington) Date: Tue, 07 May 2013 11:52:45 -0400 Subject: [PATCH 0/2] Early printk support for virtio console devices. In-Reply-To: References: <1366974299-17877-1-git-send-email-pranavkumar@linaro.org> <87obcyc9sh.fsf@rustcorp.com.au> <336C59AA-D5D7-472E-A8DA-EEB413DD6C68@suse.de> <87sj27xxjr.fsf@rustcorp.com.au> <87ip2wr8tp.fsf@rustcorp.com.au> <87txmfo0rl.fsf@rustcorp.com.au> Message-ID: <5189234D.3040208@codeaurora.org> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 05/07/2013 08:19 AM, Peter Maydell wrote: > On 7 May 2013 05:46, Rusty Russell wrote: >> Peter Maydell writes: >>> That all looks like sensible QEMU implementation possibilities >>> but it seems to be a bit of a non-sequitur from "how do we >>> tell the kernel to actually use this?" >> >> You enable the feature in the virtio console device, and a kernel >> compiled with EARLY_PRINTK will use it? > > Well, at the moment EARLY_PRINTK is hardcoded to > "use some specific UART or equivalent selected at > compile time". So the equivalent presumably would > be to hard-compile "use virtio-console", but then > how does that code know where the virtio-console > is in the address space? arm64 uses a kernel argument. Christopher -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation.