Age | Commit message (Collapse) | Author |
|
|
|
doesn't need to hold an extra reference during the call
ok deraadt@ millert@
|
|
|
|
ok deraadt@
|
|
- don't attach octrtc on the edgerouter pro either
openbsd boots fine on this system, but as there's no ethernet support yet
there's no storage at all right now.
ok pirofti@
|
|
ok pirofti@
|
|
loaded image area.
|
|
|
|
sun4m's iommu for bus_dma. (Guess what task just hit my todolist...)
|
|
ok jsing@
|
|
|
|
ok mpi@
|
|
|
|
Fixes a crash upon resume with an ATI FireMV 2400 card.
ok jsg@
|
|
|
|
causes a deadlock between reaper and zerothread I am currently investigating.
|
|
|
|
Compiles on i386, which is the only architecture where COMPAT_LINUX is
enabled at the moment.
"If it compiles, go ahead" pirofti@
|
|
From FreeBSD
ok sthen@ chris@
|
|
|
|
|
|
|
|
From Florian Riehm
|
|
|
|
Architecture Reference Specification, the sum of the 8 trap entry words
*and* of the payload which address and length are to be set at well-known
positions in the aforementioned trap entry, needs to be zero; the existing
code was only enforcing that the sum of the trap entry words is zero.
This matches what Linux and NetBSD do.
ok kettenis@
|
|
bit fields with their right sizes (the L2PARERR field on PCXL processors being
4 bits wide, not 1 bit), and make comments consistent accross these functions.
ok kettenis@
|
|
changed a lot in the last 5 years; verified to work on a 3GB system, in
snapshots for a few weeks already.
|
|
having to
modify various third party apps using the V4L2 API to build on OpenBSD specifically.
"I think this is the right thing to do" miod@
"Fine with me." sthen@
|
|
will be used from.
this adds pool_setipl at IPL_VM to the crypto descriptor pools, and
removes all the splvm handling around the use of those pools.
tested by many via tech@
ok kettenis@ deraadt@
|
|
make the crypto taskq protect things at IPL_VM instead of IPL_HIGH.
everything else in crypto.c uses splvm/IPL_VM. it seems this IPL_HIGH
came about because the hand rolled task list and thread that crypto
used to use was converted to workqs, which unconditionally used
IPL_HIGH internally. when it was converted from workqs to tasks it
blindly ported the protection workqs gave.
tested by many via tech@ and snapshots
ok kettenis@
|
|
|
|
while in the manpage add volatile where the code has it too.
ok miod@ guenther@
|
|
Both sys_mkfifo(2) and sys_mkfifoat(2) could be replace by libc wrappers
using mknodat(2) at a later date if we desire. OK guenther@
|
|
If there is a tie then a carp interface is not allowed to win even if
it has an address with a longer bitwise match. This allows reliable IPv6
communication between carp master and backup across a shared IPv6 subnet.
Consider the carp address 2001:DB8:10::14, which is configured on firewall A
(in carp master state) and firewall B (in carp backup state), each of which
has another address in the same prefix on a non-carp interface (A has
2001:DB8:10::1 and B has 2001:DB8:10::11). In this setup, A would use
2001:DB8:10::14 as source address when sending neighbour solicitations to B.
Since 2001:DB8:10::14 is a local address from B's point of view, B never
replied to the neighbour solicitations sent by A.
With this change A uses 2001:DB8:10::1 as source address instead.
ok mpi@
|
|
userland.
Fix a warning from gcc-4.9:
../../../../ufs/ufs/dir.h:113:33: warning: variably modified 'dh_firstfree' at file scope
ok kettenis@
|
|
|
|
everything else in crypto.c uses splvm/IPL_VM. it seems this IPL_HIGH
came about because the hand rolled task list and thread that crypto
used to use was converted to workqs, which unconditionally used
IPL_HIGH internally. when it was converted from workqs to tasks it
blindly ported the protection workqs gave.
tested by many via tech@ and snapshots
ok kettenis@
|
|
redundant copies of the same information. No functional change.
Also add some comments as to how these globals are used.
|
|
wasn't freeed when the interface is destroyed. Free it properly.
ok dlg
|
|
|
|
through the remainder of the attachment logic.
|
|
OK blambert@ yasuoka@
|
|
|
|
|
|
ok deraadt@
|
|
|
|
|
|
The previous lack of error handling could trigger a kernel crash
in some situations, with ulptwrite being called while not ready.
ok deraadt phessler
|
|
DMA segment size when setting up the TX buffers in msk_init_tx_ring().
ok jsg@
|
|
|