| Age | Commit message (Collapse) | Author |
|---|
|
|
|
http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-119.pdf
page 19:
Volume Space Size (BP 81 to 88)
This field shall specify as a 32-bit number the number of Logical Blocks
in which the Volume Space of the volume is recorded.
This field shall be recorded according to 7.3.3.
|
|
|
|
this avoids locking up rio when doing filename completion
on a unresponsive directory.
|
|
not very usefull at the moment as theres no code to map/unmap
memory regions right now.
|
|
|
|
|
|
|
|
|
|
converting image thru pipe would not properly restore the
original color channel on undo. like |iconv -c k8 would
still be grayscale after undo.
|
|
the issues with the previous tsc change where not related to the tsc
but where problems with timesync using an old frequency file. a
patch to fix timesync was commited, so so we reintroduce the *notsc=
again.
|
|
the frequency tolerance used by timesync was from a 10th to 10 times
the frequency of the system clock! switching a system from tsc to pic
timer changes the system clock frequency from 300MHz to arround 1.8Ghz
on a x200s laptop resulting in time running way too slow or way too fast.
so we change timesync to only accept frequencies from half to double the
system clock which still seems huge, but at least catches the case above
resulting in timesync ignoring the old frequency file.
|
|
deauthenticated by the ap
|
|
|
|
|
|
|
|
on message D reply, use 0 for txkey tsc
|
|
aux/wpa needs to reset its reply counter on deassociation to
properly restart key negotiation. we signal this with a zero
length read on the connections filtering for eapol protocol.
|
|
promisc mode prevented the call to rxon() in transmit
possibly causing association to fail while running snoopy.
|
|
allow the driver to associate the node with a new aid right after
we receive the association response, not just when we transmit
a packet which usualy does not happen as eapol is initiated by
the access point so there are no transmit calls. we just call
transmit from the wifiproc with a nil block to introduce the node.
|
|
|
|
|
|
|
|
|
|
wifictl command
|
|
add a debug flag that can be set in the ethernet options which
causes status transitions and wifictl messages to be printed.
|
|
|
|
|
|
reading wpa1oui into w, making the later memcmp with wpatkipoui
bogus.
|
|
|
|
the splhi() and apictimerlock in the Mach isnt neccesary, as
portclock always holds the ilock of the per mach timer queue
when calling timerset().
as fastticks() and the portclock timers are all handled on a
per processor basis, i think it should be theoretically possible
for the lapics to run at different frequencies. so we measure
the lapic frequency for each individual lapic and keep them in
a per processor Apictimer structure instead of assuming them
to be the same.
|
|
it is usefull to see what encryption keys have been
estabished by aux/wpa.
|
|
this makes it consistent with the manual again.
|
|
loading the divider before programming one shot mode *sometimes*
gives the wrong frequency. (X200s got 192Mhz vs. 266Mhz, after
5 boot attempts)
also reload the divider after programming periodic mode. (from
http://wiki.osdev.org/APIC_timer)
|
|
|
|
|
|
|
|
|
|
|
|
dnauthdb() would relabel expired rr's as rr->db == 0 to make
them get garbage collected by dnage(). but this doesnt work
due to dn->keep and also causes the deduplication to fail on
rrattach() as rrattach1() handles rr->dn/rr->auth as separate
name spaces.
this causes duplicate entries in the rr's when ndb gets
gets changed. to fix, we just delete the expired (removed from
ndb) rr's immidiately in dnauthdb() instead of trying trick
dnage() to garbage collect it.
|
|
|
|
doesnt seem to be reliable. also, separate tsc frequency measurement
and cpu loopconst measurement. turned out with *notsc=, the simplcycles()
calls would mess up loopconst.
|
|
we previously used tsc only on cpu kernel. now that
we use it on terminal kernel too, there might be some
surprises ahead.
so make it possible to disable tsc for machines where
the tsc rate is not kept constant across cores or is
dynamically adjusted by power management.
|
|
|
|
|
|
on terminal kernel (thank erik)
|
|
|
|
|
|
|
|
invert/shift in wrong order causing low 16 bits to be all ffff...
|
