This website requires JavaScript.
Explore
Help
Register
Sign In
upstream
/
opnsense-src
Watch
1
Star
0
Fork
You've already forked opnsense-src
0
mirror of
https://github.com/opnsense/src.git
synced
2026-05-04 17:05:14 -04:00
Code
Issues
Projects
Releases
Packages
Wiki
Activity
Actions
dfd00261c9
opnsense-src
/
usr.sbin
/
mlx5tool
/
Makefile
9 lines
88 B
Makefile
Raw
Normal View
History
Unescape
Escape
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
2018-03-08 10:21:56 -05:00
# $FreeBSD$
pkgbase: Create a mlx-tools package mlx* are only useful for users who have a Mellanox card. Create a package for it so users that don't have this card can avoid having this program. Differential Revision: https://reviews.freebsd.org/D31795
2021-09-01 13:12:09 -04:00
PACKAGE
=
mlx-tools
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
2018-03-08 10:21:56 -05:00
PROG
=
mlx5tool
MAN
=
mlx5tool.8
.
i
n
c
l
u
d
e
<
b
s
d
.
p
r
o
g
.
m
k
>
Reference in a new issue
Copy permalink