| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
The latter contains "#define _POSIX_THREADS 1" which makes gcc 2.95 complain.
|
|
|
|
|
|
for unwind-dw2.c fails to build otherwise.
|
|
be slightly more verbose and really explain what's going on.
okay millert@
|
|
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.
|
|
|
|
ok gilles@
|
|
|
|
then have to trim.
|
|
|
|
already there), and use it to locate unknown objects in the file system.
|
|
|
|
eventually, but it's enough for now to make the blocking API fully
thread-safe without locking.
|
|
|
|
unable to find a register to spill in class 'R0_REGS'
ICE when compiling PIC code. Similar to the MI targhooks.c change.
|
|
- 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.
|
|
|
|
|
|
This makes:
This terminal can only display -N processes.
a thing of the past.
|
|
|
|
I refrained from merging one patch that i dislike
and one that requires additional review,
but we are now definitely much closer to 1.12.1 than to 1.12.0.
|
|
This also backs out the realpath(3) changes for now; according to
Kristaps, they caused regressions.
|
|
which prevents filters / filenames from working from /etc/mail/aliases.
in aliases_get() during the rb tree iteration, copy the username to the
expand node.
diff from Christopher Zimmermann, thankkkks and sorry for the delay
|
|
* Replace loop with memcpy() in function get_literal()
* Style tweak: "for(" -> "for ("
From Michael W. Bombardieri
ok nicm@ millert@
|
|
Found by LLVM/Clang Static Analyzer.
ok gilles@
|
|
we can do this in the frontend; from kristaps@.
|
|
|
|
1) They consume the next argument even if it starts with a dash.
2) When -width is the last argument on the line such that the
actual width argument is missing, downgrade from a fatal to a
non-fatal error, just like for -offset. The formatting still
doesn't agree with groff, but at least we don't die any longer.
Item 2 was observed and that part of the patch coded by kristaps@,
who found lots of instances of this particular formatting error
in Mac OSX manuals.
|
|
ok krw@
|
|
ok krw@
|
