# $NetBSD: Makefile,v 1.12 2019/02/17 04:05:47 rin Exp $ # # At some point this needs to turn into linux.kmod and a proper home for it # found. For now pickup the linux_work.c from the (increasingly poorly # named) common area. # .include "../Makefile.inc" .PATH: ${S}/external/bsd/common/linux .PATH: ${S}/external/bsd/drm2/linux CPPFLAGS+= -I${S}/external/bsd/common/include CPPFLAGS+= -I${S}/external/bsd/drm2/include # XXX Kludge! CPPFLAGS+= -DDIAGNOSTIC KMOD= drmkms_linux SRCS+= linux_atomic64.c SRCS+= linux_dma_buf.c SRCS+= linux_dmi.c SRCS+= linux_fence.c SRCS+= linux_i2c.c SRCS+= linux_idr.c SRCS+= linux_kmap.c SRCS+= linux_list_sort.c SRCS+= linux_module.c SRCS+= linux_rcu.c SRCS+= linux_reservation.c SRCS+= linux_work.c # XXX Move me to linux.kmod. SRCS+= linux_writecomb.c SRCS+= linux_ww_mutex.c WARNS= 3 .include 10.99.5 NetBSD fork for lockdoc analysismerlin@scholz.ruhr
summaryrefslogtreecommitdiff
path: root/sys/rump/net/lib/liblocal/component.c
AgeCommit message (Collapse)Author
2010-03-01Introduce RUMP_COMPONENT. It behaves mostly like a simplifiedpooka
module which is linked into the kernel and cannot be unloaded. The main purpose is to get the proper constructors run and create any /dev nodes necessary for said component. Once more of the kernel (e.g. networking stack and device drivers) are converted to MODULE and devfs pops up from somewhere, rump components can be retired.
2009-05-28Use a bunch of weak symbols to determine which network componentspooka
are present. This works in userspace as opposed relying in link sets, which fail miserably. Later, when the networking stack becomes modularized, we can move to a dynamic scheme like with file systems. Also, this change allows us to do proper autoconfig, namely attach the loopback interface iff it is present.