#
4d65a7c6 |
| 24-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
usr.sbin: Automated cleanup of cdefs and other formatting
Apply the following automated changes to try to eliminate no-longer-needed sys/cdefs.h includes as well as now-empty blank lines in a row.
usr.sbin: Automated cleanup of cdefs and other formatting
Apply the following automated changes to try to eliminate no-longer-needed sys/cdefs.h includes as well as now-empty blank lines in a row.
Remove /^#if.*\n#endif.*\n#include\s+<sys/cdefs.h>.*\n/ Remove /\n+#include\s+<sys/cdefs.h>.*\n+#if.*\n#endif.*\n+/ Remove /\n+#if.*\n#endif.*\n+/ Remove /^#if.*\n#endif.*\n/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/types.h>/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/param.h>/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/capsicum.h>/
Sponsored by: Netflix
show more ...
|
Revision tags: release/14.0.0 |
|
#
1d386b48 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\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, release/11.4.0, release/12.1.0 |
|
#
8b3bc70a |
| 08-Oct-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r352764 through r353315.
|
#
eff4361d |
| 02-Oct-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Use size_t for byte_to_write variable when comparing to eeprom_info_out_len which is also size_t in mlx5tool(8).
Submitted by: slavash@ MFC after: 3 days Sponsored by: Mellanox Technologies
|
#
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
|
#
b4b75592 |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Ensure that only one command is specified at a time in mlx5tool(8).
Submitted by: kib@ MFC after: 3 days Sponsored by: Mellanox Technologies
|
#
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
|
#
ea78f07b |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Implement userspace firmware update for ConnectX-4/5/6.
Submitted by: kib@ MFC after: 3 days Sponsored by: Mellanox Technologies
|
#
b255ca09 |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Rename mlx5_fwdump_addr to more neutral mlx5_tool_addr in mlx5core.
Submitted by: kib@ MFC after: 3 days Sponsored by: Mellanox Technologies
|
#
db40c83f |
| 08-May-2019 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Fix style.
Submitted by: kib@ MFC after: 3 days Sponsored by: Mellanox Technologies
|
Revision tags: release/12.0.0, release/11.2.0 |
|
#
f3365f07 |
| 08-Mar-2018 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Check that the address is specified in mlx5tool(8).
Submitted by: kib@ MFC after: 1 week Sponsored by: Mellanox Technologies
|
#
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 ...
|