[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGCh1+kOyg45MK+pRX8HRo8LfnO3PJ-CbJCdeZ+-zzDoH6rBTg@mail.gmail.com>
Date: Thu, 30 Jul 2015 10:43:37 +0100
From: G Gregory <graeme.gregory@...aro.org>
To: Peter Maydell <peter.maydell@...aro.org>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Shannon Zhao <shannon.zhao@...aro.org>,
QEMU Developers <qemu-devel@...gnu.org>,
lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Shannon Zhao <zhaoshenglong@...wei.com>,
Igor Mammedov <imammedo@...hat.com>,
Alex Bennée <alex.bennee@...aro.org>
Subject: Re: [Qemu-devel] [PATCH v2] arm: change vendor ID for virtio-mmio
On 30 July 2015 at 10:37, G Gregory <graeme.gregory@...aro.org> wrote:
> On 30 July 2015 at 10:24, Peter Maydell <peter.maydell@...aro.org> wrote:
>> On 30 July 2015 at 09:04, Michael S. Tsirkin <mst@...hat.com> wrote:
>>> On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote:
>>>>
>>>> Why do we drop the previous way using "QEMUXXXX"? Something I missed?
>>>
>>> So that guests that bind to this interface will work fine with non QEMU
>>> implementations of virtio-mmio.
>>
>> I don't understand this sentence. If there are pre-existing
>> non-QEMU virtio-mmio implementations, then they're using
>> LNRO0005, and we should use it too.
>
> The only one I have come across is the ARM FVP model, and it happens
> that I chose the ID and maintain the tables for that so I can change
> it.
>
In fact, I would just add
Name (_HID, "QEMUXXXX")
Name (_HID, "1AF4103F")
To the tables so tables work with old (internal) kernels and new!
Graeme
--
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