6438ad3ab0
Use a driver-class module modcmd init function, instead of a socket domain init function; the socket-domain ones don't run until after configure, but we need this to be initialized before configure so that Bluetooth HCI drivers like ubt(4) can use it. This is suboptimal but it's the least intrusive way I've thought of to get this working, even if it's a little grody to make netbt a `driver-class' (builtin) module. Note that this doesn't mean netbt becomes dynamically loadable or unloadable; we're just using a module for initialization ordering. PR kern/56988 XXX pullup-10 |
||
|---|---|---|
| .. | ||
| Makefile | ||
| bluetooth.h | ||
| bt_proto.c | ||
| bt_sysctl.c | ||
| files.netbt | ||
| hci.h | ||
| hci_event.c | ||
| hci_ioctl.c | ||
| hci_link.c | ||
| hci_misc.c | ||
| hci_socket.c | ||
| hci_unit.c | ||
| l2cap.h | ||
| l2cap_lower.c | ||
| l2cap_misc.c | ||
| l2cap_signal.c | ||
| l2cap_socket.c | ||
| l2cap_upper.c | ||
| rfcomm.h | ||
| rfcomm_dlc.c | ||
| rfcomm_session.c | ||
| rfcomm_socket.c | ||
| rfcomm_upper.c | ||
| sco.h | ||
| sco_socket.c | ||
| sco_upper.c | ||