From: Luca Risolia <luca.risolia@studio.unibo.it>
To: Richard Weinberger <richard@nod.at>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
Vignesh Raghavendra <vigneshr@ti.com>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
Miquel Raynal <miquel.raynal@bootlin.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Boris Brezillon <boris.brezillon@collabora.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Ron Minnich <rminnich@google.com>, sven <sven@narfation.org>
Subject: Re: [fuse-devel] [PATCH 0/8] MUSE: Userspace backed MTD v3
Date: Tue, 9 Feb 2021 16:56:28 +0100 [thread overview]
Message-ID: <b2424246-d42b-d0bc-8951-8cefdf5b681d@studio.unibo.it> (raw)
In-Reply-To: <443281182.378615.1612885278254.JavaMail.zimbra@nod.at>
On 09/02/21 16:41, Richard Weinberger wrote:
> I wonder about the use case.
for example, many existing video applications use mmap() to map the
device memory to userspace memory. Adding support for mmap() to CUSE
would allow these apps to work without any modifications with CUSE-based
device drivers other than kernel drivers.
next prev parent reply other threads:[~2021-02-09 15:57 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 23:19 [PATCH 0/8] MUSE: Userspace backed MTD v3 Richard Weinberger
2021-01-24 23:20 ` [PATCH 1/8] fuse: Export fuse_simple_request Richard Weinberger
2021-01-24 23:20 ` [PATCH 2/8] fuse: Export IO helpers Richard Weinberger
2021-01-24 23:20 ` [PATCH 3/8] fuse: Make cuse_parse_one a common helper Richard Weinberger
2021-01-24 23:20 ` [PATCH 4/8] mtd: Add MTD_MUSE flag Richard Weinberger
2021-01-24 23:20 ` [PATCH 5/8] mtd: Allow passing a custom cmdline to cmdline line parser Richard Weinberger
2021-01-24 23:20 ` [PATCH 6/8] fuse: Add MUSE specific defines FUSE interface Richard Weinberger
2021-01-24 23:20 ` [PATCH 7/8] fuse: Implement MUSE - MTD in userspace Richard Weinberger
2021-01-24 23:20 ` [PATCH 8/8] MAINTAINERS: Add entry for MUSE Richard Weinberger
2021-01-28 10:30 ` [PATCH 0/8] MUSE: Userspace backed MTD v3 Miquel Raynal
2021-02-01 13:14 ` Richard Weinberger
2021-02-01 13:55 ` Miklos Szeredi
2021-02-09 14:26 ` Miklos Szeredi
2021-02-09 14:35 ` Richard Weinberger
2021-02-09 15:10 ` [fuse-devel] " Luca Risolia
2021-02-09 15:22 ` Miklos Szeredi
2021-02-09 15:41 ` Richard Weinberger
2021-02-09 15:56 ` Luca Risolia [this message]
2021-02-09 16:04 ` Richard Weinberger
2021-02-09 16:28 ` Luca Risolia
2021-02-09 16:29 ` Richard Weinberger
2021-02-09 16:42 ` Luca Risolia
2021-02-09 16:50 ` Richard Weinberger
2021-02-09 17:46 ` Luca Risolia
2021-02-09 19:42 ` Miklos Szeredi
2021-02-09 20:06 ` Richard Weinberger
2021-02-10 10:12 ` Miklos Szeredi
2021-02-10 11:12 ` Richard Weinberger
2021-02-10 11:16 ` Miklos Szeredi
2021-02-11 18:09 ` Miklos Szeredi
2021-04-13 12:59 ` Miklos Szeredi
2021-02-09 21:39 ` Richard Weinberger
2021-02-10 10:16 ` Miklos Szeredi
2021-02-10 11:00 ` Richard Weinberger
2021-02-10 11:14 ` Miquel Raynal
2021-02-10 11:23 ` Richard Weinberger
2021-02-10 20:55 ` Miquel Raynal
2021-02-10 21:11 ` Richard Weinberger
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=b2424246-d42b-d0bc-8951-8cefdf5b681d@studio.unibo.it \
--to=luca.risolia@studio.unibo.it \
--cc=boris.brezillon@collabora.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miklos@szeredi.hu \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=rminnich@google.com \
--cc=sven@narfation.org \
--cc=vigneshr@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).