src/sys/dev/ntb/ntb_if.m, branch main FreeBSD source tree sys: Remove $FreeBSD$: one-line sh pattern 2023-08-16T17:54:58+00:00 Warner Losh imp@FreeBSD.org 2023-08-16T17:54:58+00:00 031beb4e239bfce798af17f5fe8dba8bcaf13d99 Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/ 
Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Add driver for NTB in AMD SoC. 2019-07-02T05:25:18+00:00 Alexander Motin mav@FreeBSD.org 2019-07-02T05:25:18+00:00 6683132d54bd6d589889e43dabdc53d35e38a028 This patch is the driver for NTB hardware in AMD SoCs (ported from Linux) and enables the NTB infrastructure like Doorbells, Scratchpads and Memory window in AMD SoC. This driver has been validated using ntb_transport and if_ntb driver already available in FreeBSD. Submitted by: Rajesh Kumar <rajesh1.kumar@amd.com> MFC after: 1 month Relnotes: yes Differential Revision: https://reviews.freebsd.org/D18774 
This patch is the driver for NTB hardware in AMD SoCs (ported from Linux)
and enables the NTB infrastructure like Doorbells, Scratchpads and Memory
window in AMD SoC. This driver has been validated using ntb_transport and
if_ntb driver already available in FreeBSD.

Submitted by:	Rajesh Kumar <rajesh1.kumar@amd.com>
MFC after:	1 month
Relnotes:	yes
Differential Revision:	https://reviews.freebsd.org/D18774
Report NTB link speed to console and interface. 2017-04-23T14:25:51+00:00 Alexander Motin mav@FreeBSD.org 2017-04-23T14:25:51+00:00 48c4767756a1e2a77abfed24e34650f74ba1c540 MFC after: 2 weeks 
MFC after:	2 weeks
Once more refactor KPI between NTB hardware and consumers. 2016-07-28T10:48:20+00:00 Alexander Motin mav@FreeBSD.org 2016-07-28T10:48:20+00:00 4490696b3edf3ed9be81e695fb9dba03c94f89c8 New design allows hardware resources to be split between several consumers. For example, one BAR can be dedicated for remote memory access, while other resources can be used for packet transport for virtual Ethernet interface. And even without resource split, this code allows to specify which consumer driver should attach the hardware. From some points this makes the code even closer to Linux one, even though Linux does not provide the described flexibility. 
New design allows hardware resources to be split between several consumers.
For example, one BAR can be dedicated for remote memory access, while other
resources can be used for packet transport for virtual Ethernet interface.
And even without resource split, this code allows to specify which consumer
driver should attach the hardware.

From some points this makes the code even closer to Linux one, even though
Linux does not provide the described flexibility.
NewBus'ify NTB subsystem. 2016-07-09T11:20:42+00:00 Alexander Motin mav@FreeBSD.org 2016-07-09T11:20:42+00:00 9a5325c205f3e0088bd0be7d25185805c3bf45f0 This follows NTB subsystem modularization in Linux, tuning it to FreeBSD native NewBus interfaces. This change allows to support different types of hardware with different drivers, support multiple NTB instances in a system, ntb_transport module use for needs other then if_ntb, etc. Sponsored by: iXsystems, Inc. 
This follows NTB subsystem modularization in Linux, tuning it to FreeBSD
native NewBus interfaces.  This change allows to support different types
of hardware with different drivers, support multiple NTB instances in a
system, ntb_transport module use for needs other then if_ntb, etc.

Sponsored by:	iXsystems, Inc.