| Age | Commit message (Collapse) | Author |
|---|
|
the random subsystem as entropy. This value is pretty much unknown,
and anyways our entropy input ring does not saturate from knowns.
ok mikeb djm
|
|
No binary change.
OK ratchov@
|
|
It doesn't compile und hasn't been working during the last decade.
ok kettenis@, deraadt@
|
|
machdep.lidaction=0 # do nothing
machdep.lidaction=1 # suspend
machdep.lidaction=2 # hibernate
lidsuspend is just an alias for lidaction, so if you change one, the
other one will have the same value. The plan is to remove
machdep.lidsuspend eventually when people have upgraded their
/ets/sysctl.conf.
discussed with deraadt, who came up with the new MIB name
no objections mlarkin
ok stsp halex jcs
|
|
ok various
|
|
this means packets are consistently counted in one place, unlike the
many and various ways that drivers thought they should do it.
ok mpi@ deraadt@
|
|
|
|
methods from all audio drivers and from the audio_if structure as they
are never called.
|
|
deleted aha.h header. therefore bha must be dragged into the attic too.
|
|
|
|
order to make room for llvm. er, the llvm makefiles. er, some of them.
|
|
OK deraadt@
|
|
remove long disabled radio devices
ok deraadt
|
|
|
|
reset by mouse and keyboard instead of mouse and mouse.
|
|
already fixed in -r1.7 (for kettenis macmini), but since then the code was
heavily shuffled and moved around and this regression was re-introduced
choose a different fix now and introduce a light sensor flag for the different
models to allow or avoid the probing
prodded by landry (macmini again)
|
|
location by a comma to avoid ambiguity with newer models
hint from kettenis (last year)
|
|
|
|
ok mpi@ claudio@
|
|
all the local ones to ``nticks''.
ok stefan@, deraadt@
|
|
ok beck@ deraadt@
|
|
These files aren't USB-specific and were used by the previous
Bluetooth implementation, and will be used by the upcoming
HID-over-i2C implementation
ok deraadt
previous version ok kettenis and mpi
|
|
|
|
|
|
|
|
|
|
for-loop as acpithinkpad does
|
|
and updates is no longer needed and can be removed, so simplify things and
initialize the sensors on attach and update them through the sensors task
|
|
becomes much more reliably if we pay attention to the IBF and OBF flags.
This removes the need for excessive delays and retries, making operations
complete in microseconds instead of seconds.
This diff also removes flushing the read buffer after a read operations. This
doesn't seem to be necessary, but we might need to put that back if the
length of a reply changes for some keys.
ok jung@, deraadt@
|
|
|
|
found via key dump diff, run by Bryan Vyhmeister
also remove 3 temperature keys which likely do not return useful values
verified with help from macbook pro output of tb (4,1 and 5,5),
kettenis (12,1), and Cristoph R. Murauer (9,1) via misc@
|
|
encountered via key dump diff, run by Bryan Vyhmeister
|
|
hint from kettenis
|
|
tested by Bryan Vyhmeister, krw, tb, and myself
ok krw tb
|
|
|
|
|
|
command and propagate the result
|
|
drivers still set IFF_NOTRAILERS while others do not. Remove all usage of
the flag from the drivers which in ancient times used it (and the modern
drivers which blindly copied it from those drivers of yore).
suggested by guenther. ok mpi
|
|
|
|
|
|
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 code is refactored so the IFQ macros call newly implemented ifq
functions. the ifq code is split so each discipline (priq and hfsc
in our case) is an opaque set of operations that the common ifq
code can call. the common code does the locking, accounting (ifq_len
manipulation), and freeing of the mbuf if the disciplines enqueue
function rejects it. theyre kind of like bufqs in the block layer
with their fifo and nscan disciplines.
the new api also supports atomic switching of disciplines at runtime.
the hfsc setup in pf_ioctl.c has been tweaked to build a complete
hfsc_if structure which it attaches to the send queue in a single
operation, rather than attaching to the interface up front and
building up a list of queues.
the send queue is now mutexed, which raises the expectation that
packets can be enqueued or purged on one cpu while another cpu is
dequeueing them in a driver for transmission. a lot of drivers use
IFQ_POLL to peek at an mbuf and attempt to fit it on the ring before
committing to it with a later IFQ_DEQUEUE operation. if the mbuf
gets freed in between the POLL and DEQUEUE operations, fireworks
will ensue.
to avoid this, the ifq api introduces ifq_deq_begin, ifq_deq_rollback,
and ifq_deq_commit. ifq_deq_begin allows a driver to take the ifq
mutex and get a reference to the mbuf they wish to try and tx. if
there's space, they can ifq_deq_commit it to remove the mbuf and
release the mutex. if there's no space, ifq_deq_rollback simply
releases the mutex. this api was developed to make updating the
drivers using IFQ_POLL easy, instead of having to do significant
semantic changes to avoid POLL that we cannot test on all the
hardware.
the common code has been tested pretty hard, and all the driver
modifications are straightforward except for de(4). if that breaks
it can be dealt with later.
ok mpi@ jmatthew@
|
|
|
|
also avoid excessive tsleep()s for updates within the sensor task,
moreover this should fix some seldom seen 'comm collision' errors
|
|
|
|
ok jung@
|
|
|
|
|
