| Age | Commit message (Collapse) | Author |
|---|
|
OK espie@
|
|
Remove it from the Makefile too, unbreaking the tree.
|
|
time_second(9) has been replaced in the kernel by gettime(9).
time_uptime(9) has been replaced in the kernel by getuptime(9).
New code should use the replacement interfaces. They do not suffer
from the split-read problem inherent to the time_* variables on 32-bit
platforms.
The variables remain in sys/kern/kern_tc.c for use via kvm(3) when
examining kernel core dumps.
This commit completes the deprecation process:
- Remove the extern'd definitions for time_second and time_uptime
from sys/time.h.
- Replace manpage cross-references to time_second(9)/time_uptime(9)
with references to microtime(9) or a related interface.
- Move the time_second.9 manpage to the attic.
With input from dlg@, kettenis@, visa@, and tedu@.
ok kettenis@
|
|
OK kn@
|
|
manual pages document the same content, comparing can occasionally help
in cases of doubt, and some people may prefer one style, some the other.
While here, modernize a few .Lks from http:// to https://.
OK jmc@
|
|
|
|
|
|
|
|
time_second and time_uptime are used widely in the tree. This is a
problem on 32-bit platforms because time_t is 64-bit, so there is a
potential split-read whenever they are used at or below IPL_CLOCK.
Here are two replacement interfaces: gettime(9) and getuptime(9).
The "get" prefix signifies that they do not read the hardware
timecounter, i.e. they are fast and low-res. The lack of a unit
(e.g. micro, nano) signifies that they yield a plain time_t.
As an optimization on LP64 platforms we can just return time_second or
time_uptime, as a single read is atomic. On 32-bit platforms we need
to do the lockless read loop and get the values from the timecounter.
In a subsequent diff these will be substituted for time_second and
time_uptime almost everywhere in the kernel.
With input from visa@ and dlg@.
ok kettenis@
|
|
to commit it...
|
|
|
|
|
|
the mandoc linter is upset about "An Jason A. Donenfeld", but i'm
hoping ingo or jmc will fix it for me :)
From Matt Dunwoodie
ok deraadt@
|
|
gif used its mbuf tag to store it's interface index so it could
detect loops. gre also did this, and i cut most of the drivers
(including gif) over to using the gre tag. so the gif tag is unused.
wireguard uses the tag to store peer information between different
contexts the packet is processed in. it also needs a bit more space
to do that.
from Matt Dunwoodie and Jason A. Donenfeld
ok deraadt@
|
|
|
|
.An author Aq Mt address
|
|
|
|
|
|
- Phillips -> Philips
ok kettenis
|
|
|
|
|
|
OK deraadt@, jmc@, mpi@
|
|
prefix, and show how to use 0t for decimal (slight duplication from
the table in EXPRESSIONS but easier for the reader than sending them
off to look in a different part of the manual). ok mpi claudio jmc
|
|
it's only available on amd64 (and i386), so don't really want to
encourage it's use just yet.
|
|
|
|
i feel like ive used the word vector too much, but hopefully someone
who is good with english will check this and fix it.
|
|
|
|
|
|
requested by kettenis@
discussed with jmatthew@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Used for build systems which set paranoid permissions at build time.
See: https://marc.info/?l=openbsd-ports-cvs&m=159162220318205&w=2
original patch by jca@
|
|
|
|
but the implementation is so much more complicated.
|
|
This adds the missing TAS3004 volume control. Before, I put my ear
near the speaker (to hear audio), because I had no way to turn up the
volume. Now, the default volume is much louder, so I use sndioctl(1)
to turn it down.
Check for the model string "PowerBook5,4". This model's device tree
has compatible = "AOAKeylargo" for the audio, doesn't show the TAS3004
in the same way as other models.
|
|
|
|
|
|
|
|
|
|
ok kettenis
|
