| Age | Commit message (Collapse) | Author |
|---|
|
The global "tickadj" variable is a remnant of the old NTP adjustment
code we used in the kernel before the current timecounter subsystem
was imported from FreeBSD circa 2004 or 2005.
Fifteen years hence it is completely vestigial and we can remove it.
We probably should have removed it long ago but I guess it slipped
through the cracks. FreeBSD removed it in 2002:
https://cgit.freebsd.org/src/commit/?id=e1d970f1811e5e1e9c912c032acdcec6521b2a6d
NetBSD and DragonflyBSD can probably remove it, too.
We export tickadj via the kern.clockrate sysctl(2), so update sysctl.2
and sysctl(8) accordingly. Hypothetically this change could break
someone's sysctl(8) parsing script. I don't think that's very likely.
ok mvs@
|
|
in preparation for upcoming ACPI-attachment.
ok kettenis@
|
|
ok deraadt@
|
|
ok deraadt@
|
|
|
|
ok deraadt@
|
|
|
|
this fell out of a discussion with mortimer
ok kettenis
|
|
it's like ksyms, but different
|
|
this will make testing easier for everyone.
from Jason A. Donenfeld and Matt Dunwoodie
ok deraadt@ tobhe@
|
|
i think ive tempted fate enough for one day.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ok deraadt@
|
|
noticed by tobhe@
diff from kettenis@ (who forgot to commit this bit)
|
|
|
|
RK3399 SoC.
ok patrick@
|
|
ok tedu@ krw@ deraadt@
|
|
ok jsg
|
|
ok tedu@ jsg@
|
|
The design is fairly simple: events, in the form of descriptors on a
ring, are being produced in any kernel context and being consumed by
a userland process reading /dev/dt.
Code and hooks are all guarded under '#if NDT > 0' so this commit
shouldn't introduce any change as long as dt(4) is disable in GENERIC.
ok kettenis@, visa@, jasper@, deraadt@
|
|
This driver was never completed. It only mapped memory and established
an interrupt.
ok krw@ mlarkin@ dlg@
|
|
Not built since 2006, and a mail from 2004 mentions no one having
hardware. Unsurprisingly it does not build with clang.
ok mlarkin@ krw@ deraadt@
|
|
ok mlarkin@
|
|
ok kettenis@, semarie@, deraadt@
|
|
noone seems to use it, and we should not encourage people to use
it by having it available. it's been disabled for most of the last
release and noones asked for it in 6.6, so i'm taking that as an
ok for this removal.
|
|
|
|
|
|
gif may have needed it when you could switch modes with gif, but
now that's handled by if_etherip.c. ip_ether.c is empty, so we can
plan to remove it.
ok visa@ jca@ deraadt@
|
|
ok deraadt@
|
|
|
|
similarities between the two and using a common approach helps fixing bugs.
The new driver is better integrated with the device tree framework and
is faster (mainly because the DMA engine is configured properly now).
Tested on all currently supported variants of the hardware.
ok jsg@, jmatthew@
|
|
After removing timezone support from date(1), msdosfs, gettimeofday(2),
settimeofday(2), boot_config(8), config(8), and introducing kern.utc_offset
sysctl(2) to replace the DST/TIMEZONE options(4) to support running the RTC
at an offset from UTC, the kernel timezone is unused and we can delete it.
With this commit the kernel timezone now appears to be extinct in
upstream BSD, though it does survive in XNU:
https://github.com/opensource-apple/xnu/blob/0a798f6738bc1db01281fc08ae024145e84df927/bsd/conf/param.c#L83
Prompted by tedu@ some time back, and inspired by NetBSD and FreeBSD's
work in this area.
ok deraadt@
|
|
The DST and TIMEZONE options(4) are incompatible with KARL, so we need
some other way to compensate for an RTC running with a known offset.
Enter kern.utc_offset, an offset in minutes East of UTC. TIMEZONE has
always been minutes West, but this is inconsistent with how everyone
else talks about timezones, hence the flip.
TIMEZONE has the advantage of being compiled into the binary. Our new
sysctl(2) has no such luck, so it needs to be set as early as possible
in boot, from sysctl.conf(5), so we can correct the kernel clock from
the RTC's local time to UTC before daemons like ntpd(8) and cron(8)
start. To encourage this, kern.utc_offset is made immutable after the
securelevel(7) is raised to 1.
Prompted by yasuoka@. Discussed with deraadt@, kettenis@, yasuoka@.
Additional testing by yasuoka@.
ok deraadt@, yasuoka@
|
|
|
|
|
|
Loongson runs at 128hz. 128 doesn't divide evenly into a million,
but it does divide evenly into a billion. So if we do the per-process
itimer bookkeeping with itimerspec structs we can have error-free
virtual itimers on loongson just as we do on most other platforms.
This change doesn't fix the virtual itimer error alpha, as 1024 does not
divide evenly into a billion. But this doesn't make the situation any
worse, either.
ok deraadt@
|
|
|
|
|
|
limits. Convert kernel variables and calculations for mbuf memory
into long to allow larger values on 64 bit machines. Put a range
check into the kernel sysctl. For the interface itself int is still
sufficient. In netstat -m cast all multiplications to unsigned
long to hold the product of two unsigned int.
input and OK visa@
|
|
ok deraadt
|
|
|
|
it needs to be a bit more robust before making it more available to try.
|
|
|
|
when we have a serial console by introducing the notion of a "primary"
graphics device. The primary graphics device is the one set up and
used by firmware (BIOS, UEFI).
The goal is to make sure that wsdisplay0 and drm0 reliably attach to
the primary graphics device such that X works out of the box even
if you have multiple cards or if you are using a serial console.
This also fixes the situation where inteldrm(4) or radeondrm(4) would
take over the console on UEFI systems even if the kernel was booted
with a serial console.
ok jsg@
|
|
|
