how to encourage a wireless driver to exist?

Eduardo Morras emorrasg at
Tue Aug 19 17:14:02 UTC 2014

On Tue, 19 Aug 2014 09:44:19 -0400
Paul Kraus <paul at> wrote:

> On Aug 19, 2014, at 4:16, Eduardo Morras <emorrasg at> wrote:
> > All this description is hardware and managed by hardware.
> I would be shocked if all of the requirements of IEEE 802.11af are
> handled in the hardware! Go back and actually read and understand
> that specification. I do not expect the hardware to be querying a
> geolocation database (often multiple databases) and acting
> accordingly.

Not the requirements, but the description writed by Jerry. As I said too:

> >Except for ciphers, autentication, etc.. the same applies for/with/to the rest of your descriptions, some of them still in development. 

There are parts of the standard like autentication, geolocation you cite and other parts that managed by the driver, but those part are mostlyt hardware agnostic and works with minor changes, if any, for all drivers.

The hard part for 802.11n was done by, IIRC, Adrian Chadd and others, new drivers use the infrastructure created by them to not reimplement the wheel.

> I have been watching this specific bit of spectrum from the Wireless
> Microphone / FCC side for a decade now. If systems start coming into
> use that do NOT follow the required procedures there will be hell to
> pay as these specific frequencies are in use by lots of other users
> besides wireless networking.

When I began to use wireless, it was fantastic. Now, all my neighbours has wifi, smartphones, wireless telephones, bluetooth devices etc... and speeds went down to 500-600KB/sec. I wired again my home with gig ethernet. 0 problems.

> --
> Paul Kraus
> paul at

---   ---
Eduardo Morras <emorrasg at>

More information about the freebsd-questions mailing list