>> hca_id: mlx4_0 >> transport: InfiniBand (0) >> fw_ver: 2.6.628 >> node_guid: 0003:ba00:0100:b1d8 >> sys_image_guid: 0003:ba00:0100:b1db >> vendor_id: 0x03ba >> vendor_part_id: 25418 >> hw_ver: 0xA0 >> board_id: SUN0070000001 >> phys_port_cnt: 2 >> port: 1 >> state: PORT_ACTIVE (4) >> max_mtu: 2048 (4) >> active_mtu: 2048 (4) >> sm_lid: 1 >> port_lid: 6 >> port_lmc: 0x00 >> link_layer: IB[...] >> >> >> 2. problem: For burning the firmware I need the MFT package, right? >> But Mellanox doesn't provide it for sparc64. >> I could build the kernel modules of kernel-mft-2.7.1-7.src.rpm without any > problems. >> But the user space stuff is ppc64, x86 and x86_64 only... >> Is there maybe a possibility to get sparc64 binaries? > > You can burn FW binary image using mstflint. > Use MFT (mlxburn) to create the binary image from FW mlx file and ini file. > You > can install MFT on some Linux or Windows machine.
Hello Vladimir, thanks again for this tip! I need a "/dev/mst/mt25418_pci_cr0" when I use mstflint. Therefore I've extracted the "/etc/init.d/mst" script from the "mft-2.7.1-7.x86.rpm" which creates a "/dev/mst/mt25418_pci_cr0". But the script outputs errors and I can't use the created device: # mstflint -d /dev/mst/mt25418_pci_cr0 q Unable to parse device name /dev/mst/mt25418_pci_cr0 -E- Can not open /dev/mst/mt25418_pci_cr0: Invalid argument MFE_CR_ERROR Maybe it works when I create "/dev/mst/mt25418_pci_cr0" manually but I don't know how. So could you maybe write a short instruction list for me what I have to do after loading the mst_* modules to get the needed device file? Or do you maybe have another idea how I could flash the firmware? Regards, Lukas -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
