| Age | Commit message (Collapse) | Author |
|---|
|
drivers update hardware configuration accordingly.
tested by myself, tb@, deraadt@, abieber@
ok mpi@
|
|
another bug introduced in my turbo mode removal commit; Now fixed.
Keep the debug printf added in r1.155.
|
|
Seems to make Tx rate scaling go up faster and helps Rx performance.
ok deraadt@
|
|
For some reason we would end up passing channel number zero to
the RXON firmware command, which the firmware doesn't like.
ok sthen@ reyk@
and also tested by stefan@, deraadt@, mikeb@
|
|
|
|
ok deraadt@
|
|
ok kettenis@
|
|
tx rate retry table. This will hopefully make 11n mode work in very noisy
environments. iwm(4) already does the same.
ok kettenis@
|
|
in bsd.rd, and might uncover some bugs. Suggested by tedu@ and deraadt@.
ok sthen@ jasper@ deraadt@
|
|
Only MCS 0 to 7 are supported for now.
Tested by many. There might still be outstanding issues but they now appear
to be rare. I'm putting this in so that additional fixes can be developed
and tested more easily if required. This diff is already quite large for
one commit.
ok deraadt
|
|
there are two things shared between the network stack and drivers
in the send path: the send queue and the IFF_OACTIVE flag. the send
queue is now protected by a mutex. this diff makes the oactive
functionality mpsafe too.
IFF_OACTIVE is part of if_flags. there are two problems with that.
firstly, if_flags is a short and we dont have any MI atomic operations
to manipulate a short. secondly, while we could make the IFF_OACTIVE
operates mpsafe, all changes to other flags would have to be made
safe at the same time, otherwise a read-modify-write cycle on their
updates could clobber the oactive change.
instead, this moves the oactive mark into struct ifqueue and provides
an API for changing it. there's ifq_set_oactive, ifq_clr_oactive,
and ifq_is_oactive. these are modelled on ifsq_set_oactive,
ifsq_clr_oactive, and ifsq_is_oactive in dragonflybsd.
this diff includes changes to all the drivers manipulating IFF_OACTIVE
to now use the ifsq_{set,clr_is}_oactive API too.
ok kettenis@ mpi@ jmatthew@ deraadt@
|
|
|
|
the specific queues are ic_mgtq, ic_pwrsaveq, and ni_savedq. rtw
had its own queue for beacons.
tested by mpi@ and jmc@
ok mpi@
|
|
|
|
ok dlg
|
|
ok mikeb@
|
|
is set by the user.
previously the address read from the eeprom would also be used in discovery
frames, even if later data frames would contain the spoofed address.
ok stsp@
|
|
have any direct symbols used. Tested for indirect use by compiling
amd64/i386/sparc64 kernels.
ok tedu@ deraadt@
|
|
on every received mbuf, so there's no need to initialize this pointer in
the drivers.
Tested by and ok phessler@
|
|
|
|
when workqs were introduced, we provided a second argument so you
could pass a thing and some context to work on it in. there were
very few things that took advantage of the second argument, so when
i introduced pools i suggested removing it. since tasks were meant
to replace workqs, it was requested that we keep the second argument
to make porting from workqs to tasks easier.
now that workqs are gone, i had a look at the use of the second
argument again and found only one good use of it (vdsp(4) on sparc64
if you're interested) and a tiny handful of questionable uses. the
vast majority of tasks only used a single argument. i have since
modified all tasks that used two args to only use one, so now we
can remove the second argument.
so this is a mechanical change. all tasks only passed NULL as their
second argument, so we can just remove it.
ok krw@
|
|
|
|
ok dlg@ mpi@ bcook@ millert@ miod@
|
|
|
|
scans with various iwn(4) devices. From Fabian Raetz, testing by Fabian,
Marcin Piotr Pawlowski, Mike Burns, kettenis@ and myself. ok kettenis@ with
minor tweaks for whitespace in #define lines which I've done; also I have
done s/IWL/IWN/ in comments as noticed by dcoppa@.
|
|
|
|
after discussions with beck deraadt kettenis.
|
|
driver start routines. Instead add & use a pointer in the pkthdr
since we don't want the overhead of using a mbuf_tags(9).
claudio@ pointed out that other subsystems might want to use this
pointer too, so here's a new cookie!
ok claudio@, mikeb@, deraadt@
|
|
|
|
support. Tested by mlarkin@
|
|
of polishing from yours truly. Tested by Fabian and Benoit Lecocq.
|
|
kernel resumes normal (non-cold, able to run processes, etc) operation.
Previously we were relying on specific DVACT_RESUME op's in drivers
creating callback/threads themselves, but that has become too common,
indicating the need for a built-in mechanism.
ok dlg kettenis, tested by a sufficient amount of people
|
|
driver written by Intel engineers occasionally gets them. So when we get one,
simply reset the chip, reload the firware and bring the interface up again.
tested by stsp@, pascal@
ok stsp@
|
|
from kimberley manning
|
|
while there, fix a few %d into %u
|
|
but it reduces the diff against the FreeBSD version.
Tested on:
My Wifi Link 130.
jca@ Wifi Link 5300.
Jan Stary Wifi Link 4965 (thanks).
Adapted from FreeBSD r220894.
ok mpi@.
|
|
ok kettenis@, mpi@
|
|
don't have to. Just remove these include lines.
Compiled on amd64 i386 sparc64; OK henning@ mikeb@
|
|
ok otto
|
|
|
|
them the "normal" command to configure bluetooth coexistence fails and
makes the firmware crash. Rename the IWN_FLAG_NO_BT_COEX flag and adjust some
comments to reflect this knowledge.
ok jcs@, mikeb@, mpi@
|
|
instead of causing a firmware crash, scanning now works.
Tested by Daniel Levai.
|
|
Makes these variants actually work.
Based on a diff from James Turned, also confirmed by weerd@
|
|
committed over a 6235 device, of course.
ok deraadt@ kettenis@ stsp@ armani@
|
|
Part of the work to remove -Wno-uninitialized.
ok blambert jsg
|
|
this issue due to suspend/resume during a calibration)
ok stsp miod
|
|
now until we figure out why. This probably means the device won't function
optimally, but that's better than not functioning at all. Makes my
"Intel Centrinto Advanced-N 6205" work quite well.
|
|
firmware will crap out, at least on the 6005. First step to getting my
"Intel Centrino Advanced-N 6205" to work.
|
|
tested by many for over a week. ok kettenis@ phessler@.
|
|
contains broken data.
reported by matthew@; verified by me against Linux driver.
remove two if_ierrors++ while i'm here.
|
