how to encourage a wireless driver to exist?

Jerry jerry at
Tue Aug 19 09:53:51 UTC 2014

On Tue, 19 Aug 2014 10:16:20 +0200, Eduardo Morras stated:

>All this description is hardware and managed by hardware. The driver
>configures the hardware, gets data from it to kernel space and send data to
>it from kernel space, as each hardware has its own configuration and does
>data exchange different, you need a driver for each hardware. Sometimes,
>hardware made from the same vendor can share the same driver, but it's not a

Yes, you need the driver to make use of the hardware. Considering it took
nearly 10 years to get FreeBSD to support some, but not all "n" base
hardware when the choices where far smaller, how long will it take for it to
support, even partially the newer, more advanced ones.

I gave up years ago attempting to use FreeBSD for my wireless machines. I
absolutely refuse to be held hostage to obsolete technology. That does point
up an interesting fact that I read recently regarding various OS's, hardware,
etcetera. The FOSS has for years accused Microsoft of "lock-in", yet, by the
inability of the FOSS to develop drivers for newer hardware on a timely
basis, they are creating their own "lock-in" environment.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <>

More information about the freebsd-questions mailing list