Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758198Ab3EGMUK (ORCPT ); Tue, 7 May 2013 08:20:10 -0400 Received: from mail-lb0-f175.google.com ([209.85.217.175]:47520 "EHLO mail-lb0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755969Ab3EGMUI (ORCPT ); Tue, 7 May 2013 08:20:08 -0400 MIME-Version: 1.0 In-Reply-To: <87txmfo0rl.fsf@rustcorp.com.au> 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> From: Peter Maydell Date: Tue, 7 May 2013 13:19:46 +0100 Message-ID: Subject: Re: [PATCH 0/2] Early printk support for virtio console devices. To: Rusty Russell Cc: Alexander Graf , Pranavkumar Sawargaonkar , "linux-arm-kernel@lists.infradead.org" , "linaro-kernel@lists.linaro.org" , "patches@linaro.org" , "linux-kernel@vger.kernel.org List" , "kvmarm@lists.cs.columbia.edu" , Amit Shah Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 926 Lines: 22 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? -- PMM -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/