On 10/29/15 15:36, Gleb Smirnoff wrote:
H> The parameters for bus_bind_intr() are not available outside the
H> LinuxKPI. To support such a functionality we should wrap it, for the
H> sake of maintainability.
H>
H> The LinuxKPI is not a binary compatibility module, and will at some
H> point have API's diverging from Linux, to fit BSD API's better.
This statement makes the name of LinuxKPI quite pointless, as well
as the whole idea of the KPI unclear.
Can you please explain what is the target of LinuxKPI, then?
Hi,
The target of the LinuxKPI is at the moment to support building device
drivers and protocol layers which share code between *BSD and Linux. The
target is not to kldload a kernel object file from Linux and have it
work under FreeBSD.
For example when you build a PCI network driver, the PCI enumeration can
be shared between Linux and FreeBSD, building only OS specific network
handling on top. In the case of r290003 support is added for binding an
IRQ vector to a CPU, in a way that can easily be patched into an
existing driver using the LinuxKPI.
When you build a cross platform Linux/FreeBSD protocol stack, handling
of LIST macros, bitmaps, timers, condition variables, mutexes, threads
and so on can be shared. Like the basics of modern operating systems.
This is the Linux Kernel Programming Interface, LinuxKPI, in FreeBSD.
If you have a better name then please speak up.
--HPS
_______________________________________________
svn-src-head@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-head
To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
