05 Jul, 2015
6 commits
-
Instead of using the platform code names, use the correct platform names
to identify the respective Intel NTB hardware.Signed-off-by: Dave Jiang
Signed-off-by: Jon Mason -
This is a simple debugging driver that enables the doorbell and
scratch pad registers to be read and written from the debugfs. This
tool enables more complicated debugging to be scripted from user space.
This driver may be used to test that your ntb hardware and drivers are
functioning at a basic level.Signed-off-by: Allen Hubbe
Signed-off-by: Jon Mason -
This is a simple ping pong driver that exercises the scratch pads and
doorbells of the ntb hardware. This driver may be used to test that
your ntb hardware and drivers are functioning at a basic level.Signed-off-by: Allen Hubbe
Signed-off-by: Jon Mason -
Add module parameters for the addresses to be used in B2B topology.
Signed-off-by: Allen Hubbe
Signed-off-by: Jon Mason -
Change ntb_hw_intel to use the new NTB hardware abstraction layer.
Split ntb_transport into its own driver. Change it to use the new NTB
hardware abstraction layer.Signed-off-by: Allen Hubbe
Signed-off-by: Jon Mason -
Abstract the NTB device behind a programming interface, so that it can
support different hardware and client drivers.Signed-off-by: Allen Hubbe
Signed-off-by: Jon Mason
