Age | Commit message (Collapse) | Author |
|
|
|
the lock, but a change in member ordering meant it was using the same
address. Explicitly use different members instead of mixing address
of member and address of the lock itself.
ok miod@
|
|
of the data register, while waiting for the chip initialization to complete.
This seems to prevent spurious disappearance of le0 on some systems.
|
|
if we are running on a KA45 system. These share the KA48 board type but,
unlike KA48, can not sport frame buffers.
Prevents a bogus lcg device from attaching on KA45, and also repairs console
operation if the S3 switch is down (console on serial #0).
|
|
for, instead of zero. Makes verbose autoconf output meaningful again.
|
|
From Brad
|
|
chunk to where it should be.
From Brad
|
|
identify bad distrib scripts/tools.
ok deraadt@
|
|
the accuracy detection ALPS.
ok mpi@
|
|
also added to the other direction.
ok mikeb@
|
|
This, together with an updated xorg driver makes my drm/XVideo work.
Originally from Nigel Taylor.
ok oga@ mcbride@
|
|
__STRICT_ALIGNMENT is talking about accessing of integer types; it does
not cover doubles or floats or other things
ok miod kettenis
|
|
ok kettenis drahn
|
|
This fixed "react strangely" when the pms driver probes
for a synaptic-compatible touchpad.
Tested and ok mpi@
|
|
|
|
the alc(4) NIC while running or the NIC not working if the cable is
not plugged in upon boot up.
From Brad; tested by matteo filippetto, Gabriel Linder and edd@
|
|
inefficient but doesn't matter with reasonable numbers of interfaces.
ok dlg@
|
|
register. The spec doesn't say we have to do this while it mentions several
times one needs to wait for FR to clear after clearing FRE. The Linux driver
doesn't wait for it either. This allows us to get rid of the AHCI_F_IGN_FR
quirk.
As a side-effect this diff will probably stop ahci(4) attaching to (some)
NVIDIA fakeRAID devices. That's good since it is consistent with what we
do for Intel fakeRAID.
ok mikeb@, jmatthew@
|
|
From Christiano F. Haesbaert.
|
|
ok shadchin@ some weeks ago.
|
|
128-bit long double. Diff committed on behalf of martynas@
|
|
|
|
in DIO-II space, as a fat device spanning four select codes (i.e. 16MB of
memory). This is way too much for an at-most 2 Mpixel 8bit frame buffer, and
it turns out that this is because the device provides both a regular DIO-II
frame buffer (spanning two select codes) and a regular STI frame buffer
(spanning the other two select codes).
This commit introduces a straightforward sti@dio attachment to get a working
sti(4) and wsdisplay(4) in a ridiculously small number of lines; however
the console code needs some changes to avoid duplicating globals.
While there, add sti@dio support for the bootblocks, and I couldn't help
myself but clean the most rotten parts of them, and try to have them reuse
various files in sys/arch/hp300/dev instead of rolling their outdated ones.
Tested on a real 382 with the low-resolution frame buffer:
sti0 at dio0 scode 132: rev 8.02;129, ID 0x27134CB440A00499
sti0: 382V, 2048x512 frame buffer, 640x480x8 display
sti0: 8x16 font type 1, 16 bpc, charset 0-255
wsdisplay0 at sti0 mux 1: console (std, vt100 emulation)
Boot blocks updates tested on DIO-II 425t (serial/glass console), SGC 425e
(serial/glass console) and 382 (serial/glass console). And will be tested
on SGC 425t soon as well.
|
|
reading, and introduce a define for the DIO-II device size, as reported by
the device itself (in quarters of select code span, just to make things
more complicated than necessary).
|
|
there is no way we can tell models 360 and 362 apart by probing for an SGC
bus, or for a frodo(4) chip since of the `lil' black swan' 3x2 models, only
model 382 has frodo. So don't bother trying to tell models 360 and 362
apart, and use a common 36X symbol. No functional change except for useless
code removal.
|
|
back when I thought that these devices were showing both in DIO-II and SGC
spaces; but, as researched by tsutsui@netbsd, there is nothing in the SGC
bus address space (assuming there is SGC bus logic at all) on 3x2.
|
|
|
|
|
|
|
|
from userland, and setting it upsets the sigreturn code.
|
|
from impatiens@gmail.com
|
|
|
|
|
|
Multiplication (CLMUL) instruction found in the new Intel and
future AMD CPUs.
Done about a year ago and was rotting in my trees until Ryan
prodded Theo to read the white paper and figure out the license
issues. Apparently, there are none. All C code and SSE glue
code was written by me, while the GF multiplication function
is taken from the CLMUL white paper, specifically Figure 6:
"Code Sample - Performing Ghash Using Algorithms 1 and 5".
|
|
ok miod@, matthieu@
|
|
softdeps almost totally unusable;
|
|
requested by deraadt@
|
|
|
|
|
|
|
|
in the kernel, not only when com @ gsc is there.
|
|
in the kernel, not only when com @ gsc is there.
ok miod@
|
|
limit is reached.
Added twist, clamp the max_softdeps to 64 as it is still
possible to exhaust bufkva.
|
|
|
|
is non-NULL. Prevents a panic caused by a NULL dereference when physical
memory is exhausted at pmap_create() time.
ok kettenis@, deraadt@
|
|
|
|
ok deraadt
|
|
with the same prefix, neighbor discovery did not work. When comparing
two carp interfaces in in6_ifpprefix(), assume they share the prefix
if they have the same parent.
sure deraadt@
|
|
adding a descriptor pointing at zeroed bytes onto the end of transmit
chains. i was accounting for this extra descriptor when i was
completing the chain, but not when i was setting this up. this
meant the number of free descriptors kept growing until it overflowed.
at this point the check for space in the ring failed and packets
no longer flowed.
this counts the pad descriptor in the tx chain setup too.
ok deraadt@
|
|
|