similar to: [PATCH] virtio_mmio: add ACPI probing

On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> Added the match table and pointers for ACPI probing to the driver. >> >> This uses the same identifier for virt devices as being used for qemu >> ARM64 ACPI support. >> >>

On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> Added the match table and pointers for ACPI probing to the driver. >> >> This uses the same identifier for virt devices as being used for qemu >> ARM64 ACPI support. >> >>

On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: > Added the match table and pointers for ACPI probing to the driver. > > This uses the same identifier for virt devices as being used for qemu > ARM64 ACPI support. > > http://git.linaro.org/people/shannon.zhao/qemu.git/commit/d0bf1955a3ecbab4b51d46f8c5dda02b7e14a17e > > Signed-off-by: Graeme Gregory

On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: > Added the match table and pointers for ACPI probing to the driver. > > This uses the same identifier for virt devices as being used for qemu > ARM64 ACPI support. > > http://git.linaro.org/people/shannon.zhao/qemu.git/commit/d0bf1955a3ecbab4b51d46f8c5dda02b7e14a17e > > Signed-off-by: Graeme Gregory

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: > On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: >> >> Added the match table and pointers for ACPI probing to the driver.

On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: > On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: > > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme Gregory wrote: > >> Added the match table and pointers for ACPI probing to the driver. > >> > >> This uses the same identifier for virt devices as being used for qemu

On 2015/7/30 16:04, Michael S. Tsirkin wrote: > On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote: >> >> >> On 2015/7/30 3:16, Michael S. Tsirkin wrote: >>> ACPI spec 5.0 allows the use of PCI vendor IDs. >>> >> But virtio-mmio is not a PCI device, it's a platform device. > > Yes. ACPI spec 5.0 says: > > A valid PNP ID must

On 2015/7/30 16:04, Michael S. Tsirkin wrote: > On Thu, Jul 30, 2015 at 09:23:20AM +0800, Shannon Zhao wrote: >> >> >> On 2015/7/30 3:16, Michael S. Tsirkin wrote: >>> ACPI spec 5.0 allows the use of PCI vendor IDs. >>> >> But virtio-mmio is not a PCI device, it's a platform device. > > Yes. ACPI spec 5.0 says: > > A valid PNP ID must

On 28 July 2015 at 21:12, Peter Maydell <peter.maydell at linaro.org> wrote: > On 28 July 2015 at 11:27, Michael S. Tsirkin <mst at redhat.com> wrote: >> On Tue, Jul 28, 2015 at 11:12:33AM +0100, Peter Maydell wrote: >>> On 28 July 2015 at 11:08, Michael S. Tsirkin <mst at redhat.com> wrote: >>> > On Tue, Jul 28, 2015 at 10:44:02AM +0100, Graeme

On Mon, 2011-10-24 at 03:33 +0100, Rusty Russell wrote: > No, that's it I think. Please send a diff for the documentation, since > I'm updating the LyX master and I've already applied your previous > version. Here it goes (below). Also do you think you would be able to merge the driver (corresponding v4 patch follows) in the 3.2 merge window that seems to have just opened?

On Mon, 2011-10-24 at 03:33 +0100, Rusty Russell wrote: > No, that's it I think. Please send a diff for the documentation, since > I'm updating the LyX master and I've already applied your previous > version. Here it goes (below). Also do you think you would be able to merge the driver (corresponding v4 patch follows) in the 3.2 merge window that seems to have just opened?

On 2015/7/30 3:16, Michael S. Tsirkin wrote: > ACPI spec 5.0 allows the use of PCI vendor IDs. > But virtio-mmio is not a PCI device, it's a platform device. Why do we drop the previous way using "QEMUXXXX"? Something I missed? > Since we have one for virtio, it seems neater to use that > rather than LNRO. For the device ID, use 103F which is a legacy ID that >

of_device_id is always used as const. (See driver.of_match_table and open firmware functions) Signed-off-by: Fabian Frederick <fabf at skynet.be> --- drivers/virtio/virtio_mmio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c index 9c877d2..0ce8cda 100644 --- a/drivers/virtio/virtio_mmio.c +++

of_device_id is always used as const. (See driver.of_match_table and open firmware functions) Signed-off-by: Fabian Frederick <fabf at skynet.be> --- drivers/virtio/virtio_mmio.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_mmio.c b/drivers/virtio/virtio_mmio.c index 9c877d2..0ce8cda 100644 --- a/drivers/virtio/virtio_mmio.c +++

This patch adds an option to instantiate guest virtio-mmio devices basing on a kernel command line (or module) parameter, for example: virtio_mmio.devices=0x100 at 0x100b0000:48,1K at 0x1001e000:74 Signed-off-by: Pawel Moll <pawel.moll at arm.com> --- drivers/virtio/Kconfig | 25 ++++++ drivers/virtio/virtio_mmio.c | 170 +++++++++++++++++++++++++++++++++++++++++- 2 files

This patch adds an option to instantiate guest virtio-mmio devices basing on a kernel command line (or module) parameter, for example: virtio_mmio.devices=0x100 at 0x100b0000:48,1K at 0x1001e000:74 Signed-off-by: Pawel Moll <pawel.moll at arm.com> --- drivers/virtio/Kconfig | 25 ++++++ drivers/virtio/virtio_mmio.c | 170 +++++++++++++++++++++++++++++++++++++++++- 2 files

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git config-endian head: df43c8f58f42ec36e91740f91ea7360f63213004 commit: e1e22056bc3641f340ed27012cfd1b8b05f83a0a [38/39] fixup! virtio_net: correct tags for config space fields config: arm64-allyesconfig (attached as .config) compiler: aarch64-linux-gcc (GCC) 9.3.0 reproduce (this is a W=1 build): wget