| Age | Commit message (Collapse) | Author |
|---|
|
ddb(4) can now see static functions. That doesn't mean we should start
declaring functions as ``static'', however it helps for the few existing
exceptions.
ok deraadt@, kettenis@
|
|
|
|
This check only makes sense when a frame is saved for interrupts, not
for a (simulated) breakpoint.
This allows us to put breakpoints in interrupt context and have them
work if an interrupt fires while the CPU is idle.
|
|
An X server built after april 3 is needed to be able to start X with
the new kernel.
ok kettenis@
|
|
ok kettenis@
|
|
|
|
correctly - logically complete that now by removing MLINKS from base;
authors need only to ensure there is an entry in NAME for any function/
util being added. MLINKS will still work, and remain for perl to ease
upgrades;
ok nicm (curses) bcook (ssl)
ok schwarze, who provided a lot of feedback and assistance
ok tb natano jung
|
|
|
|
ok beck@ deraadt@
|
|
|
|
This will allow us to use some of the DDB macros on trapframe which are
not DDB_REGS.
|
|
Let's keep the 'db_' prefix for all ddb(4) functions that should not be
instrumented.
|
|
While there truncate the tables to the minimum required size; chrtoblk()
and blktochr() are designed to handle a table shorter than cdevsw.
"Looks good to me" deraadt@
|
|
were suppressed in 2011 to address a problem that has since been
solved in a more permanent way. Without the validity check proper
disklabel discovery relied on a particular I/O failure, and the I/O
failure was 'solved' by the introduction of readdisksector().
Fixes problem reading CDROM disklabels discovered by mlarkin@ while
trying to install hppa.
Compile check/typo discovery and ok 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
|
|
|
|
|
|
ok kettenis@
|
|
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@
|
|
|
|
|
|
Incoherency brought by jmc@ and schwarze@ because the SYNOPSIS of the
corresponding manual do not match its NAME.
This is one step further in the zs(4) unification... Go dokey go!
Tested by jmatthew@, ok sebastia@, deraadt@
|
|
|
|
followed by an isync.
ok mpi@
|
|
Now that "struct bpf_d" depends on <sys/srp.h> this is one of the offender
for removing the header from <sys/param.h>
|
|
a.out world.
ok deraadt@ kettenis@
|
|
|
|
as well. OK dlg@ mpi@
|
|
ok tedu@, deraadt@, miod@
|
|
|
|
LABELOFFSET and MAXPARTITIONS. Easier on the eye when scanning
through all these files. No functional change.
|
|
slightly different pattern. hppa/macppc compile and boot so
hppa64/aviion surely do too!
ok deraadt@
|
|
ok deraadt@
|
|
ok miod@
|
|
ok millert@ jasper@
|
|
|
|
headers by mistake.
|
|
|
|
ok semarie
|
|
|
|
|
|
device-tree.
With this change, supplementary PCIe cards are now properly
detected.
This should prevents the kernel from faulting when reading
unmapped PCI addresses as reported by Donovan Watteau on ppc@.
ok kettenis@
|
|
bugs@.
|
|
there's no real functional advantage to this, except that it will
make it easier to add deadlock detection to the code.
this is modelled on the c mutex implementation thats on alpha,
mips64, and hppa.
ok mpi@ kettenis@
|
|
faultbuf. But 1/ sr was only restored for machine check exceptions, and 2/ the
way it was saved was unsafe if interrupts were enabled, and could cause %r2
to be lost.
Discussing this with deraadt@ at the end of c2k15, this was probably needed
for the old VI boards which were the target of the original powerpc port,
came with a worse-than-Genesi openfirmware. Since then, machine check
exceptions have been unheard of; or, if they happen, they do not need the
status register to be restored.
ok mpi@ deraadt@
|
|
ok mpi@ looks correct miod@
|
|
|
|
On such machines the device-tree contains absolute addresses for the
various sound buttons and the hardware was not properly initiliazed.
Problem reported and fix tested by Fabian Frédérick.
|
|
kernels and we no longer have any.
|
