| Age | Commit message (Collapse) | Author |
|---|
|
IP22 motherboard (IP26, IP28). Instead, do not ask for a BUS_DMA_COHERENT
mapping, but perform explicit cache operations.
This removes the need for the memory controller to switch between `fast' and
`slow' mode every time a DMA descriptor is updated.
Tested on IP22 and IP28.
|
|
Emulate W mode if a Synaptics model doesn't provide it, and check
for the success of the resolution query during setup.
ok shadchin@, mpi@
|
|
The ALPS mechanism for gesture detection can produce long delays between
a packet that signals a tap and the next packet, which either signals
the end of the gesture or the start of a drag-operation. The time spans
can exceed the timeouts used by the generic detection mechanism in the
synaptics driver. Reporting both the touch and the release event when
the second packet has arrived ensures that the tap will be recognized.
ok mpi@ shadchin@
|
|
default). From Matthew Martin on tech@
|
|
|
|
|
|
|
|
for upcoming CompCert port.
Final version of the diff is from kettenis@ with input from jsg@ and tedu@.
ok kettenis@, jsg@, "I agree" millert@
|
|
isn't brought in by inteldrm or radeondrm.
|
|
backend allocoter here without passing PR_WAITOK to pool_init(9).
ok mikeb@
|
|
Drop the explicit pool backend allocator here and add PR_WAITOK to the
flags passed to pool_init(9).
The pfi_addr_pl and pf_rule_pl can get used in interrupt context though.
So simply drop the explicit pool backend allocator without adding PR_WAITOK
to the flags passed to pool_init(9).
ok mikeb@
|
|
|
|
control for wskbd. This may fix "record level" keys on certain
keyboards.
|
|
Fix a regression reported by Brad.
|
|
ok mlarkin@
|
|
ok deraadt@
|
|
submitting a bulk write request.
This also means big bulk write requests are no longer split into
multiple small transfers something that libusb consumers do not
expect.
From Grant Czajkowski <czajkow2 AT illinois DOT edu> as part of the
GSoC 2015.
|
|
length of the key as argument.
This way every consumer of the radix tree has a chance to explicitly
initialize the shared data structures and no longer rely on another
subsystem to do the initialization.
As a bonus ``dom_maxrtkey'' is no longer used an die.
ART kernels should now be fully usable because pf(4) and IPSEC properly
initialized the radix tree.
ok chris@, reyk@
|
|
Issue reported by semarie@ on bugs@ who also isolated the
use-after-fruit to pflow(4) using dlg@'s tracing mbuf diff.
Inputs from and ok florian@, semarie@, benno@
|
|
tedu tested an almost identical diff from brad that set the same flags.
|
|
ok millert@, tedu@, mlarkin@
|
|
This should get mail from the mailing lists flowing again. Thanks to
millert@ for helping me tracking this down.
ok millert@, tedu@, mlarkin@
|
|
else!
ok deraadt@
|
|
::1 configured before fe80::1.
(lo0:0) in pf should resolve to 127.0.0.1 ::1.
reported by and ok mikeb@
|
|
compiles on more than one platform.
|
|
and skip completed transfers in dwc2_abort_xfer(). This fixes some
timeout-related crashes.
Feedback and ok mpi@
|
|
Found the hardway by naddy@
|
|
field in struct usbd_xfer which is part of dwc2_xfer.
ok mpi@
|
|
possible lock recursion panic on transfer timeout. The lock is not
needed yet because the USB stack is not MP-safe.
ok mpi@, "makes sense" jasper@
|
|
|
|
This introduces a behavior change as we now reject !RTF_UP routes to
output packets. This stricter check exposed a bug in the setup of
new routes and was the reason for the previous revert. This should
be now fixed by r1.229 of sys/net/route.c .
ok bluhm@
|
|
This makes dhclient(8) configured default routes usable without relying
on the link-state change hooks not present in RAMDISK kernels.
ok krw@, claudio@
|
|
EFI Loaded Image Device Path Protocol typically includes partition and file
components. We want to match it to a "raw" Device Path without these
components though, so we declare we have found the boot device as soon as
the Device Path matches the initial components of the Loaded Image Device Path.
ok yasuoka@
|
|
|
|
submitting a read request.
This also means big read requests are no longer split into multiple
small transfers something that libusb consumers do not expect.
Tested by ajacatoutot@.
Found by Grant Czajkowski <czajkow2 AT illinois DOT edu> during the
GSoC 2015.
|
|
ok gerhard uebayasi deraadt
|
|
use atomic operations to operate on pm_stats.resident_count. Is it really
necessary to keep track of that for the kernel pmap?
|
|
something that points smack in the middle of the buffer.
|
|
|
|
|
|
|
|
|
|
|
|
log atempts. sendsyslog(2) is a good place to detect and report
the problem.
OK deraadt@
|
|
configured networks on RAMDISK kernels.
The problem is that the default route installed by dhclient(8) does not
have the RTF_UP flag in this environement and rtisvalid(9) doesn't allow
you to use a RTF_DOWN route.
|
|
|
|
ok deraddt
|
|
|
|
|
|
Also fix the boot from BIOS and bump the version.
input and ok deraadt
|
