#
b2c76c41 |
|
16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line nroff pattern Remove /^\.\\"\s*\$FreeBSD\$$\n/
|
#
280f34c3 |
|
13-Jul-2022 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
cuse(3): Make some clarifications in the manual page. MFC after: 1 week Sponsored by: NVIDIA Networking
|
#
58a8f6e9 |
|
18-Jul-2022 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
cuse(3): Allow allocating a memory buffer of exactly 2 GBytes. The manual page date will be bumped separately. MFC after: 1 week Sponsored by: NVIDIA Networking
|
#
2ca43c3d |
|
13-Jul-2022 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
cuse(3): Make cuse_vmfree() NULL safe. MFC after: 1 week Sponsored by: NVIDIA Networking
|
#
db92a6cd |
|
18-Apr-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Implement flag for telling cuse(3) clients if the peer is running in 32-bit compat mode or not. This is useful when implementing compatibility ioctl(2) handlers in userspace. MFC after: 1 week Sponsored by: Mellanox Technologies
|
#
9f16d9c9 |
|
05-Oct-2017 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Add support for new cuse(3) error code, CUSE_ERR_NO_DEVICE. This error code is useful when emulating Linux input event devices from userspace. PR: 218626 Submitted by: jan.kokemueller@gmail.com MFC after: 1 week Sponsored by: Mellanox Technologies
|
#
df2d82e0 |
|
23-Jun-2014 |
Joel Dahl <joel@FreeBSD.org> |
mdoc: remove superfluous paragraph macros.
|
#
b5112faf |
|
05-Jun-2014 |
Christian Brueffer <brueffer@FreeBSD.org> |
Mdoc cleanup, typo and grammar fixes.
|
#
fa0f6e62 |
|
23-May-2014 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Initial import of character device in userspace support for FreeBSD. The CUSE library is a wrapper for the devfs kernel functionality which is exposed through /dev/cuse . In order to function the CUSE kernel code must either be enabled in the kernel configuration file or loaded separately as a module. Currently none of the committed items are connected to the default builds, except for installing the needed header files. The CUSE code will be connected to the default world and kernel builds in a follow-up commit. The CUSE module was written by Hans Petter Selasky, somewhat inspired by similar functionality found in FUSE. The CUSE library can be used for many purposes. Currently CUSE is used when running Linux kernel drivers in user-space, which need to create a character device node to communicate with its applications. CUSE has full support for almost all devfs functionality found in the kernel: - kevents - read - write - ioctl - poll - open - close - mmap - private per file handle data Requested by several people. Also see "multimedia/cuse4bsd-kmod" in ports.
|