| #
353240 |
|
07-Oct-2019 |
hselasky |
MFC r352983 and r353001:
Move EEPROM information query from a sysctl in mlx5en(4) to an ioctl
in mlx5core. The EEPROM information is not only a property of the
mlx5en(4) driver.
Submitted by: slavash@
Sponsored by: Mellanox Technologies
|
| #
347869 |
|
16-May-2019 |
hselasky |
MFC r347313:
Implement firmware reset from userspace in mlx5tool(8).
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
347841 |
|
16-May-2019 |
hselasky |
MFC r347288:
Implement userspace firmware update for ConnectX-4/5/6.
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
347840 |
|
16-May-2019 |
hselasky |
MFC r347287:
Rename mlx5_fwdump_addr to more neutral mlx5_tool_addr in mlx5core.
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
347797 |
|
16-May-2019 |
hselasky |
MFC r347247:
Add MLX5_FPGA_RELOAD IOCTL(2) to mlx5fpga.
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
341966 |
|
12-Dec-2018 |
hselasky |
MFC r341576:
mlx5fpga: Add set and query connect/disconnect FPGA
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
341964 |
|
12-Dec-2018 |
hselasky |
MFC r341575:
mlx5fpga: IOCTL for FPGA temperature measurement
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
341962 |
|
12-Dec-2018 |
hselasky |
MFC r341574:
mlx5fpga: Support MorseQ board
Added and supported new enum "morseQ = 4" for fpga_id field
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
341960 |
|
12-Dec-2018 |
hselasky |
MFC r341573 amd r341643:
mlx5fpga_tools initial code import.
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
341958 |
|
12-Dec-2018 |
hselasky |
MFC r341572 and r341590:
mlx5fpga: Initial code import.
Submitted by: kib@
Sponsored by: Mellanox Technologies
|
| #
331586 |
|
26-Mar-2018 |
hselasky |
MFC r330653:
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@
Sponsored by: Mellanox Technologies
|