Use IOCONF #define to determine component name.

Avoids having to manually retype info already in .ioconf.

Also, COMPONENT_SIMPLE -> RUMP_COMPONENT=simple. That way, we can add
other attributes where necessary. As "future directions", the "ioconf"
attribute for RUMP_COMPONENT can just be removed when a driver is
converted to modular and has a proper modcmd.

Make it easier to create rump kernel components, part 1.

Reduce copypasteware for the component constructors. If a constructor
calls only config_init_component(), handle it from a common source file
instead of copying the same(ish) file around to every component.

Add a COMMENT describing what each component roughly does.

"make describe" prints the comment.

Requested/inspired by Vincent Schwarzer on rumpkernel-users

branches: 1.3.2; 1.3.4; 1.3.6; 1.3.24; 1.3.42;
Remove unused opt_bluetooth.h

plunky: "feel free"

Include bthub support.

As mario knows, it should be in another component, but just cram
it here for now until someone solves kernel module dependencies
for us.

USB bluetooth device rump component.

This is a curious driver in the sense that unlike all other current
device drivers, it does not require vfs. This is because the driver
is controlled via bluetooth, which is controlled via PF_BLUETOOTH
sockets (as opposed to a /dev node).

branches: 1.2.2; 1.2.4; 1.2.6;
Include bthub support.

As mario knows, it should be in another component, but just cram
it here for now until someone solves kernel module dependencies
for us.

USB bluetooth device rump component.

This is a curious driver in the sense that unlike all other current
device drivers, it does not require vfs. This is because the driver
is controlled via bluetooth, which is controlled via PF_BLUETOOTH
sockets (as opposed to a /dev node).

Remove shlib_version files and just use Makefile SHLIB_MAJOR/MINOR,
with the default provided by Makefile.rump (they're all 0.0 anyway)

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.24; 1.1.42;
USB bluetooth device rump component.

This is a curious driver in the sense that unlike all other current
device drivers, it does not require vfs. This is because the driver
is controlled via bluetooth, which is controlled via PF_BLUETOOTH
sockets (as opposed to a /dev node).

Make it easier to create rump kernel components, part 1.

Reduce copypasteware for the component constructors. If a constructor
calls only config_init_component(), handle it from a common source file
instead of copying the same(ish) file around to every component.

branches: 1.4.2; 1.4.4; 1.4.6; 1.4.24; 1.4.42;
Catch up with cosmetic changes to output from config(1)

use config_init_component()

Include bthub support.

As mario knows, it should be in another component, but just cram
it here for now until someone solves kernel module dependencies
for us.

USB bluetooth device rump component.

This is a curious driver in the sense that unlike all other current
device drivers, it does not require vfs. This is because the driver
is controlled via bluetooth, which is controlled via PF_BLUETOOTH
sockets (as opposed to a /dev node).