[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFEAcA9h8iSYfTBtf6n+Vk5sDtBR2yB2oafRxikHoWbKt0VRUw@mail.gmail.com>
Date: Thu, 2 May 2013 11:06:09 +0100
From: Peter Maydell <peter.maydell@...aro.org>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: Alexander Graf <agraf@...e.de>,
Pranavkumar Sawargaonkar <pranavkumar@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linaro-kernel@...ts.linaro.org" <linaro-kernel@...ts.linaro.org>,
"patches@...aro.org" <patches@...aro.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
"kvmarm@...ts.cs.columbia.edu" <kvmarm@...ts.cs.columbia.edu>
Subject: Re: [PATCH 0/2] Early printk support for virtio console devices.
On 1 May 2013 03:07, Rusty Russell <rusty@...tcorp.com.au> wrote:
> An emergency output is a reasonable idea, and this is a reasonable
> implementation. The question is practical: will it be used? Because we
> don't implement reasonable ideas which aren't going to be used.
If you think it fits reasonably into the virtio spec (ie doesn't
implement things at the wrong level of the transport/backend
abstraction) then we can implement it in QEMU, and I think it
makes more sense to do this than to throw in a random extra
serial port.
To be actually useful we need to also specify something in
the device tree to say "here is where you will find your
emergency output and what it is".
thanks
-- PMM
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists