On Mon, 10 Feb 2025 15:26:27 +0800
Wenbo Cao <caowe...@mucse.com> wrote:
> For This patchset just to support the basic chip init work
> and user can just found the eth_dev, but can't control more.
> For Now just support 2*10g nic,the chip can support
> 2*10g,4*10g,4*1g,8*1g,8*10g.
> The Feature rx side can support rx-cksum-offload,rss,vlan-filter
> flow_clow,uncast_filter,mcast_filter,1588,Jumbo-frame
> The Feature tx side can support tx-cksum-offload,tso,vxlan-tso
> flow director base on ntuple pattern of tcp/udp/ip/ eth_hdr->type
> for sriov is also support.
>
> Because of the chip design defect, for multiple-port mode
> one pci-bdf will have multiple-port (max can have four ports)
> so this code must be care of one bdf init multiple-port.
Driver errors on most basic build (gcc-14 x86)
[2394/3266] Compiling C object drivers/net/rnp/base/librnp_base.a.p/rnp_mbx.c.o
../drivers/net/rnp/base/rnp_mbx.c: In function ‘rnp_write_mbx_pf’:
../drivers/net/rnp/base/rnp_mbx.c:323:51: warning: array subscript 64 is above
array bounds of ‘struct rnp_mbx_sync[64]’ [-Warray-bounds=]
323 | struct rnp_mbx_sync *sync = &hw->mbx.syncs[mbx_id];
| ~~~~~~~~~~~~~^~~~~~~~
In file included from ../drivers/net/rnp/base/rnp_mbx.c:7:
../drivers/net/rnp/base/rnp_hw.h:57:29: note: while referencing ‘syncs’
57 | struct rnp_mbx_sync syncs[RNP_MBX_FW];
| ^~~~~
../drivers/net/rnp/base/rnp_mbx.c: In function ‘rnp_read_mbx_pf’:
../drivers/net/rnp/base/rnp_mbx.c:282:51: warning: array subscript 64 is above
array bounds of ‘struct rnp_mbx_sync[64]’ [-Warray-bounds=]
282 | struct rnp_mbx_sync *sync = &hw->mbx.syncs[mbx_id];
| ~~~~~~~~~~~~~^~~~~~~~
../drivers/net/rnp/base/rnp_hw.h:57:29: note: while referencing ‘syncs’
57 | struct rnp_mbx_sync syncs[RNP_MBX_FW];
| ^~~~~
[3266/3266] Linking target app/dpdk-test
