From: Antony Pavlov <antonynpavlov@gmail.com>
To: Ahmad Fatoum <ahmad@a3f.at>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 9/9] virtio: virtio-pci: restrict MIPS support to MMU configuration
Date: Tue, 2 Mar 2021 17:28:14 +0300 [thread overview]
Message-ID: <20210302172814.ac8a31bd01efa18df2065992@gmail.com> (raw)
In-Reply-To: <20210228190836.1451663-9-ahmad@a3f.at>
On Sun, 28 Feb 2021 20:08:36 +0100
Ahmad Fatoum <ahmad@a3f.at> wrote:
Hi!
> MMU-less MIPS doesn't play along nicely with VIRTIO_PCI.
> e.g. Reading from a virtio-rng, will return clearly bogus data.
> Document this in the Kconfig, so no one else trips over this.
>
> Eventually, this should be fixed..
Please describe, how can I reproduce the problem.
>
> Signed-off-by: Ahmad Fatoum <ahmad@a3f.at>
> ---
> drivers/virtio/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index ecf66987b3ed..91a89d3e1b89 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -28,6 +28,7 @@ config VIRTIO_MMIO
> config VIRTIO_PCI
> tristate "PCI driver for virtio devices"
> depends on PCI && HAS_DMA
> + depends on MMU && MIPS || !MIPS
> select VIRTIO
> help
> This driver provides support for virtio based paravirtual device
> --
> 2.30.0
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-03-03 16:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 19:08 [PATCH 1/9] virtio: align virtio_config_ops::generation return type with Linux Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 2/9] virtio: remove unused, left-over, virtio_config_ops::set_features Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 3/9] hw_random: virtio: simplify code Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 4/9] dma: move dma_map/unmap_single from ARM to common code Ahmad Fatoum
2021-03-03 12:08 ` Sascha Hauer
2021-03-03 16:12 ` [PATCH] " Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 5/9] virtio: ring: fix erroneous behavior around caches and MMU Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 6/9] virtio: fix support for big-endian clients Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 7/9] PCI: port Linux pci_find_capability Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 8/9] virtio: support virtio-based device drivers over PCI Ahmad Fatoum
2021-02-28 19:08 ` [PATCH 9/9] virtio: virtio-pci: restrict MIPS support to MMU configuration Ahmad Fatoum
2021-03-02 14:28 ` Antony Pavlov [this message]
2021-03-03 17:10 ` Ahmad Fatoum
2021-03-01 16:29 ` [PATCH 1/9] virtio: align virtio_config_ops::generation return type with Linux Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210302172814.ac8a31bd01efa18df2065992@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=ahmad@a3f.at \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox