... because some of the 802.11p NICs are actually ath5k NICs that have
the relevant bandpass filters for 5.9GHz and high output amplifiers.
-a
On 17 February 2014 01:27, Holger Schurig wrote:
> Okay, I admit that I cannot help you, I have no clue on the driver level.
>
> But maybe I can help
Hi,
There are a few things you can do to better understand the driver code.
First, knowing how the actual wireless chips works will help you to
understand what the driver is trying to accomplish. You can find some of
the manuals online. For example, for the AR5213:
http://read.pudn.com/downloads89
Hi,
Disclaimer: I have no experience with the ath5k driver. That said, to debug
the issue you can create a debugfs entry to read the current value of the
register. Then you can double check that you're correctly writing to it,
and that no other code is overwriting your changes. Doing that might
in
Hi,
There is a AR5K_DIAG_SW_5211 register in ath5k codebase (in reg.h) .
I am using AR5212 NIC and even if I set all the bits of diagnostic register
to be zero,
my wireless works correctly.
I wanted to know if I have to set some other things in the codebase in
order for changes made in this registe
Okay, I admit that I cannot help you, I have no clue on the driver level.
But maybe I can help with the methodology. :-)
You mention 802.11p (car-to-car-communication). Is there any specific
reason you base it on ath5k and not on ath9k? If you look at the
number of commits, then you should see t
