• Ivo van Doorn's avatar
    rt2x00: Fix rt2400pci signal · 89993890
    Ivo van Doorn authored
    After sampling hundreds of RX frame descriptors,
    the results were conclusive:
    - The Ralink documentation regarding the SIGNAL and RSSI are wrong.
    It turns out that of the 5 BBR registers, we should not use BBR0 and BBR1
    for SIGNAL and RSSI respectively, but actually BBR1 and BBR2.
    BBR0 does show values, but the exact meaning remains unclear,
    but they cannot be translated into a SIGNAL or RSSI field.
    BBR3, BBR4 and BBR5 are always 0, so their meaning is unknown.
    As it turns out, the reported SIGNAL is the PLCP value, this
    in contradiction to what was expected looking at rt2500pci which
    only reported the PLCP values for OFDM rates and bitrate values
    for CCK rates.
    This means we should let the driver raise the flag about the contents
    of the SIGNAL field so rt2x00lib can always do the right thing based
    on what the driver reports.
    Signed-off-by: default avatarIvo van Doorn <IvDoorn@gmail.com>
    Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
rt2400pci.c 47.7 KB