Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758107Ab3DSJbG (ORCPT ); Fri, 19 Apr 2013 05:31:06 -0400 Received: from mail-la0-f47.google.com ([209.85.215.47]:39558 "EHLO mail-la0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758023Ab3DSJbD (ORCPT ); Fri, 19 Apr 2013 05:31:03 -0400 MIME-Version: 1.0 In-Reply-To: <20130419092752.GB13283@mudshark.cambridge.arm.com> References: <1366264344-28025-1-git-send-email-pranavkumar@linaro.org> <20130419090558.GA13283@mudshark.cambridge.arm.com> <20130419092752.GB13283@mudshark.cambridge.arm.com> From: Peter Maydell Date: Fri, 19 Apr 2013 10:30:40 +0100 Message-ID: Subject: Re: [RFC] arm64: Early printk support for virtio-mmio console devices. To: Will Deacon Cc: Pranavkumar Sawargaonkar , "linaro-kernel@lists.linaro.org" , Patch Tracking , Marc Zyngier , "linux-kernel@vger.kernel.org" , "kvmarm@lists.cs.columbia.edu" , "linux-arm-kernel@lists.infradead.org" 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: 916 Lines: 20 On 19 April 2013 10:27, Will Deacon wrote: > On Fri, Apr 19, 2013 at 10:25:35AM +0100, Pranavkumar Sawargaonkar wrote: >> I am not against using 8250 emulation (as far as it solves printk >> issues for kernel booting logs), but my point is why not to add early >> read-write support for virtio console, which also can be useful in >> emulation less mach-virt environment also ? > > We can have both, but only one of those requires a change to the virtio > specification. I don't think avoiding writing a spec is necessarily a good reason for insisting on emulation of a lump of hardware 95% of whose capabilities you aren't going to use... -- 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/