| Age | Commit message (Collapse) | Author |
|---|
|
there is probably a new EEPROM format here, but i don't know how to parse
the AR5424 version yet, so just set some defaults for these chipsets for now.
|
|
commented out, remove it. Unifdef TFS while there.
ok marco@ krw@
|
|
- Don't reload the watchdog timer in case there are still unhandled
descriptors.
- Don't clear IFF_OACTIVE unless there are at least 6 free TX
descriptors. The function dc_encap() will bail if there are
only 5 or fewer free TX descriptors, causing dc_start() to
abort so it makes no sense to pretend we could process mbufs
again when in fact we can't.
- Always assign idx to sc->dc_cdata.dc_tx_cons; it doesn't make
much sense to exclude the idx == sc->dc_cdata.dc_tx_cons case.
From FreeBSD
|
|
|
|
stopped nor the waiting state and also no other means to check
whether the receiver is idle, we have no choice but to call
mii_tick unconditionally even in the case of the DC_REDUCED_MII_POLL
handling as far as the RX side is concerned. This isn't necessarily
worse than checking whether RX is idle though because unlike as
with TX we're racing with the hardware, which might receive packets
any time while we poll the MII, anyway. Fixes the use of trunk(4)
with the affected interfaces.
From FreeBSD
|
|
Really just the low-hanging fruit of (hopefully) forthcoming timeout
conversions.
ok art@, krw@
|
|
and transmitter to idle state times out for chips where the status
bits in question never change (observed in detail with DM9102A) and
therefore the warning would highly likely be a false positive.
From FreeBSD
|
|
This requires that structures defined within __packed structures must
independently request that they themselves become __packed, too.
worked on with toby
CVS: ----------------------------------------------------------------------
|
|
Tested by ckuethe@ and many users, thanks!
|
|
sc_print_addr(); ok krw@
|
|
|
|
drivers can report 2-3x times the number of actual packets being
transmitted by only incrementing the counter for descriptors with
buffers being freed.
ok kettenis@
|
|
PHY. This helps with systems dual booting Windows XP/Vista where the
Windows drivers will put the PHY in power down mode when rebooting.
From FreeBSD
|
|
to the Attic. nothing uses it in the tree and it is very unlikely
that something will use it one day.
the only driver supporting FHSS PHYs in the tree is ray(4) and it
does not use net80211.
|
|
for now because it needs more testing, but basic WPA/WPA2 and WEP
seems to work. to enable it, set the compiled-in ath_softcrypto
variable to 1.
this is based on a previous diff from damien@ with some changes to
disable the hardware crypto engine if softcrypto is enabled and to
keeps the hardware crypto code in place to allow later work on
hardware WPA/WPA2.
|
|
|
|
"The driver lets you change to Host AP mode, but it does not work
and it probably never will."
so just remove the HOSTAP capability bit in the code and remove this
sentence.
|
|
one function. Also fix reception of multicast packets when in promisuous
mode. The Realtek chips are a little different than most others in that
they will not receive multicast packets by enabling promiscuous mode
alone.
Tested by naddy@ and sthen@
ok naddy@
|
|
|
|
|
|
|
|
use it in drivers that leave the 802.11 FCS in frames
passed to radiotap BPF. otherwise, userland has no way
to know if FCS is included or not as it depends on drivers.
this is required by some ports (aircrack).
requested by dhill@
|
|
bwi_node structure (containing the rate control state).
because bwi(4) does not support HostAP or IBSS modes there is
no need to maintain a per-node rate control state, so we could
as well store it in bwi_softc but that will allow for future
improvements.
pointed out by Taylor R Campbell (campbell AT mumble DOT net)
on tech@
|
|
remove IBSS and HostAP support from net80211 and 802.11 drivers.
it can be used to shrink RAMDISK kernels for instance (like what
was done for wi(4)).
it also has the benefit of highlighting what is specific to IBSS
and HostAP modes in the code.
the cost is that we now have two code paths to maintain.
|
|
1. If bus_dmamap_load_mbuf() fails because there are not enough
segments in the map, defrag the mbuf.
2. If there are not enough free (hardware ring) descriptors, set
IFF_OACTIVE and keep the packet on the queue.
3. If there is some other resource starvation that makes
bus_dmamap_load_mbuf() or defragmentation fail, drop the packet.
Don't set IFF_OACTIVE, since the Tx ring could be empty and we'd be
stuck.
4. Only pass packets that are actually handed off to the hardware to
BPF. Do so before handing them off to the hardware to make sure
the packet isn't freed behind our back.
ok dlg@
|
|
|
|
|
|
when acting as an access point instead of having each driver doing the
job.
tested by krw@ (ral AP) and me with several drivers.
|
|
From FreeBSD
|
|
state with the newly minted link flag in the softc's rl_flags
field.
Tested by fkr@
|
|
Tested by naddy@
From FreeBSD
|
|
The current method results in a MAC address of all zeros.
Tested by bernd@/jcs@ with 8102E and fkr@ with 8168C.
From FreeBSD
ok jsg@
|
|
prints it. These should be the last offenders.
|
|
|
|
with different versions for various ar5212 variants and add an extra
table for PCI-E devices. This fixes support for various newer devices
(like the 1st generation MacBook, T61 variants) but it still does not
work on a number of other devices.
Tested by many
ok deraadt@
|
|
pointers we don't own, but the autoconf machinery does.
|
|
on an attachment dependent flag; the Tadople SPARCLE needs it.
ok kettenis@ deraadt@
|
|
RX/TX configuration registers to 128 instead of 512 bytes.
- add a few more MAC/RF id strings for the dmesg.
- check for PCI-E instead of single chip variants in a few places.
ok deraadt@
|
|
|
|
|
|
ok mglocker
|
|
ok krw@, dlg@
|
|
import some fixes for 1T2R adapters from the linux vendor driver.
|
|
pass a pointer to an ieee80211_rxinfo structure containing those two
fields plus an extra flags field that indicates whether the frame was
decrypted by hardware or not.
required for a future fix.
|
|
ok jsg@
|
|
halfway through. Makes the ISP12160 correctly load its firmware again on
sparc64.
ok krw@
|
|
For now, only one such flag is defined, PCKBC_CANT_TRANSLATE. It hints
pckbc that the device does not behave correctly to the ``set translation''
commands.
Set this flag if we are running on a Tadpole Ultrabook machine, which needs it.
This makes the built-in keyboard work correctly on this laptop (with the
help of the software translation pckbd diff).
tested & ok kettenis@
|
|
newer PCI Express adapters (ie 8168C*/8102*) work.
V2 Checksum offload format in RTL8102 devices not yet supported.
No objections from brad@. Thanks to everyone who tested.
|
|
upcoming changes and sort list.
|
|
|
