Document support for the BCM4378 / BCM4387 chipsets.

from Brad

revert previous, stsp made WEP work on bwfm(4)

WEP in bfwm(4) never worked, sync with reality

"ifconfig bwfm0 [-]nwkey ..." does not work and thus the installer no longer
offers WEP, so unmention support while leaving the recommendation against it.

tweak previous: update .Bl -column line

Show which bwfm(4) chipsets are 11n and which are 11ac. ok miod@

adjust Xr for fw_update to section 8;
ok afresh sthen deraadt

Teach modern "inet autoconf"

This goes in line with hostname.if(5), unwind.conf(5), ifconfig(8)
as well as our installer.

OK deraadt

Fix a bunch of typos in various man pages.

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

revert previous, stsp made WEP work on bwfm(4)

WEP in bfwm(4) never worked, sync with reality

"ifconfig bwfm0 [-]nwkey ..." does not work and thus the installer no longer
offers WEP, so unmention support while leaving the recommendation against it.

tweak previous: update .Bl -column line

Show which bwfm(4) chipsets are 11n and which are 11ac. ok miod@

adjust Xr for fw_update to section 8;
ok afresh sthen deraadt

Teach modern "inet autoconf"

This goes in line with hostname.if(5), unwind.conf(5), ifconfig(8)
as well as our installer.

OK deraadt

Fix a bunch of typos in various man pages.

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

tweak previous: update .Bl -column line

Show which bwfm(4) chipsets are 11n and which are 11ac. ok miod@

adjust Xr for fw_update to section 8;
ok afresh sthen deraadt

Teach modern "inet autoconf"

This goes in line with hostname.if(5), unwind.conf(5), ifconfig(8)
as well as our installer.

OK deraadt

Fix a bunch of typos in various man pages.

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

adjust Xr for fw_update to section 8;
ok afresh sthen deraadt

Teach modern "inet autoconf"

This goes in line with hostname.if(5), unwind.conf(5), ifconfig(8)
as well as our installer.

OK deraadt

Fix a bunch of typos in various man pages.

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

Teach modern "inet autoconf"

This goes in line with hostname.if(5), unwind.conf(5), ifconfig(8)
as well as our installer.

OK deraadt

Fix a bunch of typos in various man pages.

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

Fix a bunch of typos in various man pages.

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

Fix .Bl header label used for alignment in bwfm(4) supported device table.

"network adapters" supported by bwfm(4) are in fact "wireless network adapters"

Document chipsets supported by bwfm(4).
ok jmc@ deraadt@
"thanks and don't wait for me" patrick@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

for the net80211 drivers supporting WPA, update to a new unified text showing
that WPA1 is disabled by default, and provide a couple of extra pointers about
configuration. direction of change proposed by stsp, ok jmc stsp

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

patrick confirms that this driver does not support powersave;

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

adjust hostname.if examples to show "wpakey" on the same line as "nwid"

OK jmc@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

Include the standard string mentioning 802.11 versions in bwfm(4)'s
description, to aid searches. ok and reminder for usb(4) and pci(4) jmc@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@

SDIO support for bwfm(4) is good enough now that we can remove the
claim saying it is not supported. It's slowly getting on par with
the other busses but there's still more work to do.

Prompted by tb@

Update manpage to reflect changes to bwfm(4) which allow Host AP mode
and the PCI attachment driver.

Add a PCI attachment driver for bwfm(4). It's not finished, but it's
already past the point where development can occur out of the tree.
With this I can successfully scan for access points and tell the chip
to attach to an SSID. RX path should work as well, but since I forgot
to bring the antenna with me to my parents, the reception is a bit
horrible in the metal enclosure.

There are a few reasons this driver is rather big. First we set up the
ARM Cores, uploading the firmware and kicking it off. Then we need to
read all needed information from the registers. Once that is done we
have to set up countless buffers. There are 2 TX rings and 3 RX rings,
plus N TX rings for the actual data that is yet to be implemented.

Merry Christmas!

ok kettenis@

List bwfm(4) in usb(4).

Prompted by and ok jmc@

Fix grammar mistake I was supposed to fix before committing.

Add bwfm(4) manpage.

ok stsp@