| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
note that this does not affect sys (which already uses those flags) and libc
(which has its own special target for them). just other uses of
bsd.{prog,lib,dep}.mk.
"I suppose" deraadt@, "yes, we want that" marco@
From Toni Mueller, thanks!
|
|
Don't trunc_page when determining the highest address to alloc. it is
not what pglistalloc expects and pmemrange will fail that allocation.
For consistency, if we fail to alloc under 16meg then alloc high as
assume we'll bounce (same as i386 and amd64)
ok deraadt@
|
|
ok deraadt@
|
|
bus_dmamem_map can fail for a myriad of reasons already, so panicing if
pmap fails is just impolite. other archs will be forthcoming.
ok krw@, art@ before lock
|
|
note, only the pcidevs for those chipsets that have been tested are
enabled for now. Please contact me if you have a r600 or r700 that does
not attach radeondrm. Only the 2D/Xv bits are here. I'm ambivalent about
the implementation of the RADEON_CS ioctl for OpenGL since that was
originally kernel-modesetting only. When we update mesa I shall think
about (and test) it.
Tested by quite a number. Zero bad reports. Nagged perpetually by
robert@ (and probably others) for months now.
|
|
|
|
ok otto@
|
|
installed on a softraid volume. This is work in progress but can continue
in tree.
ok marco@
|
|
checking for underruns when decrypting packets.
ok beck@ "sure" deraadt@
|
|
call session_close(nbr) instead since only that will do all needed cleanup.
Still not prefect but at least the lde is no longer eating all CPU when a
session times out. OK michele@
|
|
file descriptor. If not done, we will loop forever on this event.
OK michele@
|
|
|
|
we may actually hit the end of the tree (at least in theory).
|
|
* additional predefined strings needed for Perl manuals,
now also supported by mandoc(1) - but not recommended for
general use because they are non-portable
* remove irrelevant STANDARDS
ok jmc@
|
|
ok marco@ jmc@
|
|
Also add a new optional metadata type for boot data. This is the first
step (of many) towards being able to boot from softraid volumes.
WARNING: This version of the softraid metadata is not compatible with
previous versions. As a result, any softraid volumes created with older
kernels will not assemble. Data on existing softraid volumes should be
backed up before upgrading. The volume should then be recreated and the
data restored.
ok marco@
|
|
|
|
top(1) and ps(1) now display the same info.
ok tedu@ millert@ otto@ and tested on sparc64 by landry@
|
|
argument to allow skipping past values in a buffer
|
|
|
|
- BCM5709S (id from FreeBSD, for fibre bnx)
- BCM5481/5482 (id from Linux, low-power PHY, for embedded boards etc)
|
|
* much improved pod2man support and low-level roff robustness
* have -Tlint imply -Wall and -fstrict
* use fewer macros and more enum in libman
* and various bug fixes
|
|
implies ", " is acceptable as a separator, which it's not. ok djm@
|
|
|
|
use a stack buffer; ok dtucker@
|
|
This is mostly cleanup by kristaps@ after my rather hackish patch
to tolerate the non-text macros .na, .sp, .br in next-line scope;
plus some nesting issues fixed by him, all in man(7).
This survived a full cd /usr/src; make man.
|
|
|
|
|
|
Based on a comparison with the apm code.
ok deraadt@, kettenis@
|
|
1) when you have a wrapper function in a dmatag that just calls the
_bus_dmamem original, you don't need it, just put the original function
in the tag
2) don't trunc_page the avail_end/ISA_BOUNCE_THRESHOLD stuff (see icb
for a discussion of why this is wrong about 00:00 gmt). make i386 and
amd64 both do this the same (the amd64 way is cleaner and makes the
third diff actually possible without a lot of pain). just do
dmamem_alloc_range(0, threshold) and if that fails do a alloc_range(0,
-1) and assume we'll bounce to pick up the pieces. Also using avail_end
for alloc_range is not nice (miod has been trying to avoid these abuses
iirc), so just use (paddr_t)-1, which is equivalent since you want "any"
memory.
3) now this is the funny one. consider point 2. then considering why
using the same bloody function to allocate your bouncebuffer is just
f'ing wrong. instead allocate with alloc_range(0, threshold) to make
sure that our bouncebuffer is actually uner 16megs.
ok deraadt@, kettenis@. Tested by several people.
|
|
instead, use "\e". This patch does not change rendering with (g)roff,
but it lets mandoc render the page correctly.
ok jmc@
|
|
ncpufound before counting, because it defaults to 1 (for those
architectures which do not count)
ok kettenis
|
|
ok armani
|
|
|
|
phones.
ok armani
|
|
translit(`ab',`aa',`cd') -> `cb'
(first occurrence matches)
okay miod@, sthen@
fixes minor autoconf issues, like HAVE_VOID__ instead of HAVE_VOID_P
|
|
some programs working correctly in tmux and screen.
From the readline changelog:
w. Fixed a bug in the callback read-char interface to make it work when a
readline function pushes some input onto the input stream with
rl_execute_next (like the incremental search functions).
ok deraadt
|
|
ISC dhclient had a buffer overflow:
http://www.kb.cert.org/vuls/id/410676
and while our dhclient is not vulnerable to that, it got us looking at
how the subnet mask option is handled. this limits specific ip
address options to length 4 in conformance with RFC 2132. discussion
started by william@ and with input from krw@
ok krw@
|
|
|
|
ok kettenis@
|
|
|
|
prefix/len and nexthop but do not consider the priority. send_rtmsg() needs
to use the kroute element and not the one sent from the LDE since that one
has no priority set (which is needed). This seems to solve a problem where
ldpd modified the wrong routes. OK michele
|
|
ok jmc@
|
|
|
|
revision, in the code searching for the end of a sentence
|
|
ok guenther@
|
|
non-empty line to form one single line, as required by XPG 4.
While here, use isblank(3) to identify white space instead of assuming
that only blank and tab are white space characters.
Geoff Clare <gwc at opengroup dot org> agrees that the standard for -L
should say "A line is considered to end with the first <newline>
unless the last character of the line is an *unescaped* <blank>;
an *unescaped* trailing <blank> signals continuation to the next
non-empty line, inclusive." The word *unescaped* is missing from
the standard, but we regard that as a goof in the standard.
Bug noticed by, much feedback from, and "should go in now" guenther@
|
|
|
