| Age | Commit message (Collapse) | Author |
|---|
|
OK claudio@
|
|
|
|
|
|
to scan for the product ID again.
|
|
the sc_devs array.
|
|
|
|
on the written buffers. Use the flag for writes from the page daemon to
ensure that we free buffers written out by the page daemon rather than
caching them.
ok kettenis@
|
|
|
|
|
|
|
|
in pppxopen(). ok dlg@ yasuoka@
|
|
|
|
Logic controllers, taken from the Linux kernel.
ok mpi@
|
|
|
|
- Allocate/enable sensors wich match both: the static usage table of supported
usage IDs and the usages supported by the device;
- Do not attach when no sensors can be allocated;
- Makes device querying smarter: query the device just once for values stored
in the same reportid reply payload.
- Use sensor_status.
ok mpi@
|
|
socket.
OK claudio@
|
|
|
|
call tsleep(9) on resume. deraadt@ pointed that this not needed
for powerdown since `cold' is set.
Another approach would be to call delay() directly in the reset
functions, but let stay coherent with the other HC drivers.
|
|
localhost connections.
The plan is to always use the routing table for addresses and routes
resolutions, so there is no future for an option that wants to bypass
it. This option has never been implemented for IPv6 anyway, so let's
just remove the IPv4 bits that you weren't aware of.
Tested a least by lteo@, guenther@ and chrisz@, ok mikeb@, benno@
|
|
|
|
|
|
matter if we don't see ourselves, and if we pick another starting point, the
first port we see might disappear half way through (I have seen this happen),
which makes it more complicated to identify when we're back at the start.
|
|
ok mpi@ yuo@
|
|
ok kettenis@
|
|
add that, don't try loading firmware for them.
|
|
|
|
the interrupt handler as well. See rev 1.12.
|
|
Also fixes a possible memory leak where m doesn't get freed in bail case.
"lets do it like this" claudio@
|
|
for later reuse in udp_output().
"Apart from that OK" claudio@
|
|
Make sure that in_pcbbind() is called from in_pcbconnect() by KASSERTing that
local port == 0 implies an unspecified local address.
OK claudio@
|
|
in uvm_pmr_rootupdate(). Issue spotted and fix provided by Kieran Devlin.
|
|
|
|
even comment the lines.
|
|
|
|
firmware (2048 for 2k login firmware, 256 otherwise)
pointed out by deraadt@, ok dlg@
|
|
is currently being covered by the wired TLB entries, flush them, so that,
if the process' pc is still running in a vulnerable page, the WAR will
reapply immediately and fault the next page.
|
|
the usual 1.1 coprocessor mask, instead of using zero and having every
userland process dying with signal 4.
The circumstances under which this call fails are unclear and could be
tied to specific PROM version (I have tried overzealous stack alignment and
other tricks, to no avail). Interestingly enough, the 715/75 system which
hits this problem, only triggers it when booting from disk, and never when
booting from network.
This diff is an ugly bandaid until the problem is better understood. Or maybe
it is not worth investigating, seeing that Linux hardcodes the coprocessor
mask and never issues PDC_COPROC calls; I wonder what HP/UX does.
In my tree for over 18 months; "Looks like a nice hack" deraadt@
715/75 system provided by Sebastiaan Indesteege, thanks!
|
|
interrupt is routed through the ISA PIC, the interrupt is edge-triggered
(despite PCI interrupts being level-triggered).
Attempt to recognize this and correctly setup the PIC ELCR register to `edge'.
This allows ES40 systems (and maybe others, but apparently all the other alpha
systems with on-board M5237 correctly route its interrupt as a PCI interrupt)
to reliably boot multiuser without suffering from USB interrupt storms (this is
especially noticeable when using glass console which, unlike serial console,
does not trigger other interrupts to give other devices a chance to run).
However, this is not enough yet to allow for proper USB device usage; your
mileage may vary.
Tested by bluhm@ and me. Putting it early in the release cycle so that
regressions on other systems, if any, can hopefully get noticed soon enough.
|
|
interrupt. With this we can talk to Hitachi disk arrays, which sometimes
return so much sense data that a status continuation response is generated
in addition to the normal status response.
tested by deraadt@
|
|
panic with pppx when using npppd with multiple pppx devices.
This is triggered when pppxclose() is called on device that hasn't
been opened causing a NULL dereference and panic. Avoid
this by returning ENXIO if the device has not been opened.
ok yasuoka@
|
|
scsibus. this lets path drivers get matched instead of just sd(4).
ask mpath to maybe swap a path with a disk via mpath.
ok deraadt@
|
|
|
|
|
|
|
|
reaper from hogging the cpu. it will do the kernel lock twiddle trick to
allow other CPUs a chance to run, and also checks if the reaper has been
running for an entire timeslice and should be preempted.
ok deraadt
|
|
(then immediately reacquire it). this has the effect of giving interrupts
on other CPUs to a chance to run and reduces latency in many cases.
ok deraadt
|
|
which is the default, unless the fault call is explicitly used to wire a given
page.
The amount of pages being faulted in was borrowed from the FreeBSD VM code,
about 15 years ago, at a time FreeBSD was only reliably running on 4KB page
size systems.
It is questionable whether faulting the same amount of pages, on platforms
where the page size is larger, is a good idea, as it may cause too much I/O.
Add an uvmfault_init() routine, which will compute the proper number of pages
at runtime, depending upon the actual page size, and attempting to fault in
the same overall size the previous code would have done with 4KB pages.
ok tedu@
|
|
ok jmatthew@
|
|
|
|
|
