| Age | Commit message (Collapse) | Author |
|---|
|
.S code when masking the upper bits, instead of hardcoding them. Makes code
easier to understand (and also I might have a need to reduce PFN width on
some particular CPU models in the future).
No change in generated code.
|
|
the size (internalized ones can be larger on some architectures) for
fitting into the socket. Avoid getting confused by sb_hiwat as well.
This fixes a variety of issues where sendmsg() would fail to deliver
a fd set or fail to wait; even leading to file leakage.
Worked on this with claudio for about a week...
|
|
to a trap)' dance before invoking trapsignal(), which will mess with the pc
too. My bug initially, can't believe I never noticed; fixed first in NetBSD.
This makes libsqlite3 build.
|
|
ok deraadt, miod, guenther
|
|
the other uses.
ok mikeb@
|
|
values in () for consistency.
diff from Michael W. Bombardieri.
ok sthen dlg mikeb
|
|
so don't incorrectly assume both channels are disabled on these controllers.
ok jsg@
|
|
anticipation of further changes to closef(). No binary change.
ok krw@ miod@ deraadt@
|
|
ok deraadt@
|
|
|
|
|
|
|
|
|
|
to pass both the virtual and physical addresses of the page to clean to
SyncDCachePage, which is the only routine using `Index' operations on the data
cache, which might be virtually indexed at some levels but physically indexed
at others. On the other hand, it does not make any sense to pass a physical
address to routines using `Hit' operations (and they were discarding them
anyway).
In addition to making things cleaner, this fixes sporadic userland misbehaviour
(read: SIGSGEV) on RM7000 O2 systems.
|
|
|
|
8:8:8, and use the fast putchar code unconditionally: it turns out it
expects the background color as 4:8:4. This fixes the `character background
is too green and too light' effect that caused this code path to only be used
for black background, and the slower code for the rest.
|
|
|
|
behalf of curproc.
|
|
|
|
(That means the misplaced optimization is back in.) It broke mips and
possibly other architectures.
|
|
bus-specific attachment; impactreg.h and impactvar.h move from sgi/xbow/ to
sgi/dev/.
Teach the generic impact code how to code with pre-ImpactSR boards, which have
a slightly different register layout (information obtained from Peter Fuerst's
Linux IP28 patches).
Add an impact@gio attachment (unfortunately untested, no Impact GIO boards
here). All Indigo 2 graphics options should be supported now (assuming the
Extreme/Ultra will actually work with grtwo(4) out of the box).
Tested not to disturb operation on IP30.
** ATTENTION! If you are building IP27 or IP30 kernels, be sure to rm impact.d
** before building a new kernel.
|
|
is disabled, and nothing shows up on the monitor in this case. To be
investigated later.
|
|
|
|
register.
|
|
files, for them to become useful.
|
|
|
|
NetBSD driver, with the infinite loops removed, the negative heights fixed,
and the explicit delay() calls removed. And support for fonts wider than
8 pixels.
|
|
identifier is actually the first word of the boards' shared ram, and might
have a legit value. Be sure to probe for the signature register before
deciding we have found a GIO board.
While there, if we have a glass console attached, don't bother probing it
again at autoconf time, since we have already identified it.
|
|
and can return completely bogus values; writing these values back to the
register can have unexpected and hilarious side effects, such as disabling the
frame buffer.
Workaround this `feature' by reading the register in a loop until we read
twice the same value, and the value looks legit; then cache this value in a
global variable and handle the register from now on, as a write-only register.
|
|
thread information.
Add a KERN_PROC_SHOW_THREADS flag that has to be set in order to get the
thread info and make it off by default. This creates backwards compatibility
for applications that relied on a given size/number of items to be returned.
Modify ps(1) and top(1) accordingly.
Okay guenther@.
|
|
From NetBSD.
|
|
The optimization goes through great lengths to use less optimized code
paths in place of the simple path, where the latter is actually faster.
ok tedu, guenther
|
|
setting %fs, resulting in it not getting restored properly later
ok mikeb@ deraadt@
|
|
only. Ported from NetBSD, not tested due to lack of hardware, hopefully it
will be working as intended (fingers crossed)
|
|
where applicable (i.e. Indy only).
|
|
temporarily disabled (and then reenabled later). Will be necessary for the
next driver commit.
|
|
ok miod@
|
|
|
|
obviously can occur after the transfer complete. In this case, don't
print a warning (if MIDI_DEBUG defined) and don't attempt to stop the
transfer twice.
|
|
(NG1, XL, XGE) frame buffer.
Adapted from NetBSD; newport extended to support underline and fonts wider than
8 pixels, such as the default 12x22 Gallant font. Framebuffer depth computation
seems to be wrong on Indy models, to be investigated later (but doesn't prevent
text console from working).
|
|
false positives.
Do not look for framebuffers past GIO EXP1, there shouldn't be anything there.
Add the console code machinery to attach a glass console on IP22, when the
appropriate drivers will exist.
On multihead systems, get console framebuffer address (well, sort of) from a
completely undocumented interface (knowledge taken from Linux, confirmed to
work on a dual-head Indigo 2 here).
While there, get frame buffer names from ARCBios whenever possible, to be used
in dmesg eventually.
|
|
initial setup to be complete before switching to our trap handlers.
However, change guarded_{read,write}_* to clear BEV in the coprocessor 0
status register, and restore it afterwards, to use our fault handlers within
these functions. This makes these functions usable from consinit().
|
|
these among frame buffer drivers. No functional change.
|
|
layout in 64-bit mode. Found the hard way, of course.
|
|
- break each hpc1/hpc3 child lists into two lists, one for the onboard
devices, and one for the expansion devices.
- do not try to attach Indy-only devices (pckbc, haltwo) on Challenge S.
- do not duplicate entries for expansion devices, only with different interrupt
numbers depending on the system, but instead use a single entry with -1 as
the interrupt level, and have the attachment glue figure out which
interrupt vector applies, depending upon the system.
- on expansion hpc1 (or 1.5) boards, do a minimal bus check to decide whether
or not the hardware we are attaching is there, since we currently don't
know how to tell E++ (sq only) and GIO32 SCSI (wdsc only) boards apart.
This hopefully will get rid of misleading `device not configured' messages.
|
|
IP20, IP22 and IP24, and provide the necessary macros to compute interrupt
vectors numbers (from the int.c point of view) from given sources.
|
|
to make the hpc3 bus_space_tag (similar to the imc one except for the
bus_space_barrier method) a global, compile-time known, object; which will in
turn help getting glass console to work (pckbc will depend on this).
|
|
need to have knowledge of the underlying interrupt controller. No functional
change.
|
|
invoke bufadjust() accordingly. Similar to what sysctl kern.bufcachepercent
does.
|
|
|
