On 2019-03-06 1:44 p.m., Serge Semin wrote: > Alas the test driver is not going to work with IDT NTB hardware, > since it uses Spad only, which aren't supported by IDT devices. IDT NTB > PCIe functions provide message registers to communicate with peers. See > ntb_perf driver code for reference of portable driver design. > > In order to make the test driver portable the following alterations > are needed: > 1) Add NTB Message register API usage together with Scratchpad+Doorbell. > 2) When NTB MSI library is updated with functions like > ntb_msi_peer_setup_mws()/ntb_msi_peer_clear_mws() they are needed to be > utilized in the test driver as well to set a translation address on the > peer side. Per, the discussion on the previous email, we can update this later once we actually have sensible infrastructure for it. The mess in ntb_perf is not something I want to replicate and we don't have any interest in creating a large amount of infrastructure to support hardware we don't care about. Logan
