|
Revision tags: release/13.4.0 |
|
| #
2878d99d |
| 12-Sep-2024 |
Graham Percival <gperciva@tarsnap.com> |
manuals: Misc macro typos
These were reported by `mandoc -T lint` as
ERROR: skipping unknown macro
When these pages were rendered with `man`, the "unknown macro" meant
that the entire line was o
manuals: Misc macro typos
These were reported by `mandoc -T lint` as
ERROR: skipping unknown macro
When these pages were rendered with `man`, the "unknown macro" meant
that the entire line was omitted from the output.
Obvious typos in:
lib/libsys/swapon.2
lib/libsys/procctl.2
share/man/man9/firmware.9
lib/libcasper/services/cap_net/cap_net.3: 'mode' describes a function
argument.
lib/libsys/statfs.2: there's no .Tm command ("trademark?"), and
.Tn ("tradename") is deprecated, so remove the macro entirely.
usr.sbin/mfiutil/mfiutil.8: man was interpreting '/dev/' as a macro
(which it didn't recognize).
share/man/man4/qat.4: same issue as above, but with '0'. In this case,
given the context of the previous line, rewriting as "Value '0'"
seemed more appropriate.
usr.sbin/mlx5tool/mlx5tool.8: typo in .Xr
Signed-off-by: Graham Percival <gperciva@tarsnap.com>
Sponsored by: Tarsnap Backup Inc.
Reviewed by: concussious, imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1417
show more ...
|
|
Revision tags: release/14.1.0 |
|
| #
1a720cbe |
| 15-May-2024 |
Alexander Ziaee <concussious@runbox.com> |
man filesystems: fix xrefs after move to section 4
Reviewed by: des, imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1077
|
|
Revision tags: release/13.3.0, release/14.0.0 |
|
| #
fa9896e0 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: two-line nroff pattern
Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/
|
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0, release/13.0.0, release/12.2.0 |
|
| #
3d265fce |
| 09-Oct-2020 |
Gordon Bergling <gbe@FreeBSD.org> |
Fix a few mandoc issues
- skipping paragraph macro: Pp after Sh
- sections out of conventional order: Sh EXAMPLES
- whitespace at end of input line
- normalizing date format
|
|
Revision tags: release/11.4.0, release/12.1.0 |
|
| #
8b3bc70a |
| 08-Oct-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r352764 through r353315.
|
| #
133fc15c |
| 02-Oct-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Add the ability to query the EEPROM information in mlx5tool(8).
Submitted by: slavash@
MFC after: 3 days
Sponsored by: Mellanox Technologies
|
|
Revision tags: release/11.3.0 |
|
| #
7648bc9f |
| 13-May-2019 |
Alan Somers <asomers@FreeBSD.org> |
MFHead @347527
Sponsored by: The FreeBSD Foundation
|
| #
998c9a2b |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Implement firmware reset from userspace in mlx5tool(8).
Submitted by: kib@
MFC after: 3 days
Sponsored by: Mellanox Technologies
|
| #
ff08edcb |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Document userspace firmware flash in mlx5tool(8) and mlx5io(4).
Submitted by: kib@
MFC after: 3 days
Sponsored by: Mellanox Technologies
|
| #
fc39af04 |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Fix typo.
Submitted by: kib@
MFC after: 3 days
Sponsored by: Mellanox Technologies
|
|
Revision tags: release/12.0.0, release/11.2.0 |
|
| #
e808190a |
| 08-Mar-2018 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Add kernel and userspace code to dump the firmware state of supported
ConnectX-4/5 devices in mlx5core.
The dump is obtained by reading a predefined register map from the
non-destructive crspace, ac
Add kernel and userspace code to dump the firmware state of supported
ConnectX-4/5 devices in mlx5core.
The dump is obtained by reading a predefined register map from the
non-destructive crspace, accessible by the vendor-specific PCIe
capability (VSC). The dump is stored in preallocated kernel memory and
managed by the mlx5tool(8), which communicates with the driver using a
character device node.
The utility allows to store the dump in format
<address> <value>
into a file, to reset the dump content, and to manually initiate the
dump.
A call to mlx5_fwdump() should be added at the places where a dump
must be fetched automatically. The most likely place is right before a
firmware reset request.
Submitted by: kib@
MFC after: 1 week
Sponsored by: Mellanox Technologies
show more ...
|