| Age | Commit message (Collapse) | Author |
|---|
|
all jumbled up in the same functions. the rtc (mc chip) and clock (i8243)
startup was also mixed up. they the soft state and hardware state can
be started in the right order, and it is easy to restart just the
neccessary parts upon resume. tested in numerous cases:
(apic, pic) * (GENERIC.MP, GENERIC) * (mp, non-mp) * (i386, amd64)
ok kettenis
|
|
|
|
new features:
* support the .in macro in man(7)
* support minimal PDF output
* support .Sm in mdoc(7) HTML output
* support .Vb and .nf in man(7) HTML output
* complete the mdoc(7) manual
bug fixes:
* do not let mdoc(7) .Pp produce a newline before/after .Sh; reported by jmc@
* avoid double blank lines related to man(7) .sp and .br
* let man(7) .nf and .fi flush the line; reported by jsg@ and naddy@
* let "\ " produce a non-breaking space; reported by deraadt@
* discard \m colour escape sequences; reported by J.C. Roberts
* map undefined 1-character-escapes to the literal character itself
maintenance:
* express mdoc(7) arguments in terms of an enum for additional type-safety
* simplify mandoc_special() and a2roffdeco()
* use strcspn in term_word() in place of a manual loop
* minor optimisations in the -Tps and -Thtml formatting frontends
|
|
confusion. Fixes at least my usb DVD reader and The Blue Tick.
|
|
scsi_inquire_vpd(). scsi_inquire_vpd() oddness noted by jsg@ after
report of macppc problems by kili@.
|
|
-Wsystem-headers and -std=c99, where GCC 4.2 would warn that it couldn't
give us C99 inline semantics.
ok guenther@, dcoppa@, millert@, deraadt@
|
|
|
|
UVIDEO_FLAG_FIX_MAX_VIDEO_FRAME_SIZE quirk.
|
|
|
|
in the former, so switch an example that needs them to use printf instead.
From bcr at freebsd.org.
ok halex@
|
|
Symptoms noted by oga@. actual bug spotted by dlg@
|
|
|
|
at end of file' warnings. Simplify the shell quoting to make it easier
to read while we're at it
"looks allright" beck@
|
|
|
|
sensorsd to do actions when docking or undocking.
ok jordan
|
|
extensions: __real__ and __imag__ operators, the use of '~' for
complex conjugation, and 'i' or 'j' as a suffix for complex constants.
While this doesn't handle folding and overflow detection for complex
constants correctly, it's good enough to make it through libm...and
found several bugs once it could do so.
"no objections" miod@, krw@
|
|
|
|
tweak to eliminate an 'else' clause.
|
|
stdin up to the server, I forgot one essential point - the tmux server
could now be both the producer and consumer. This happens when tmux is
run inside tmux, as well as when piping tmux commands together.
So, using stdio(3) was a bad idea - if sufficient data was written, this
could block in write(2). When that happened and the server was both
producer and consumer, it deadlocks.
Change to use libevent bufferevents for the client stdin, stdout and
stderr instead. This is trivial enough for output but requires a
callback mechanism to trigger when stdin is finished.
This relies on the underlying polling mechanism for libevent to work
with whatever devices to which the user could redirect stdin, stdout or
stderr, hence the change to use poll(2) over kqueue(2) for tmux.
|
|
|
|
devices.
An upcoming fix for some problems with the client stdout/stderr handling
relies on it working, so make tmux force libevent to use poll(2) via
EVENT_NOKQUEUE, until we have fixed kqueue.
|
|
|
|
myself" panics that some people have seen over the last year-and-a-half.
Cherry picked from a more complex (and therefore scarier) diff from oga@.
ok tedu@, oga@
|
|
|
|
|
|
|
|
|
|
the start and queued the command for processing by userland later.
the adapter could stop running between the check and the queue.
this merges the state and queue mutexes and combines the check and
queue ops in vscsi_cmd into the same critical section.
tweaked by and ok matthew@
|
|
will integrate with pkg_add output (no more disturbed error messages
from wrong subject lines)
|
|
(which krw is the lucky owner of) this requires a much bigger hammer. we
have to reset it and put it back into the right mode
ok krw
|
|
|
|
sizeof(char *), not in bytes, so we've been allocating and copying around
four or eight times as many bytes as we needed to
ok kettenis@ deraadt@
|
|
initialization strategy, rather than pretending to do user reference
counting. Previously, we would re-initialize the SCSI pool(9)s, which
had the fun consequence of causing sysctl(kern.pool.npools) to
infinite loop at IPL_VM.
ok krw@
|
|
is currently done in the latest versions of GNU patch.
Please watch out for output appearing out-of-order.
Discussed with millert and deraadt.
OK deraadt
|
|
PR 6288.
ok deraadt
|
|
ok deraadt
|
|
"feel free!" deraadt
|
|
OK nicm
|
|
responses. Yes, they are violating the rfc's. Yes they do exist anyway.
Also fix a memory leak when url_encode fails to malloc, by simply
err'ing out if so.
feedback and ok phessler@
|
|
can be a normal situation and will allow a local/authenticated user to
trigger the fatal on purpose ...
ignore permanently failed bounce deliveries since there's not much smtpd
can do anyway, that's what the previous queue code did.
experienced and reported by pirofti@
|
|
cvs/rcs.
OK xsa zinovik
|
|
ok deraadt
|
|
Fix naming & order of tag to be clear
ok deraadt
|
|
This ensures that we reach the call to reboot(2) without being killed
by some other process. OK deraadt@ nicm@
|
|
uaudioreg.h. sorry about that.
sync endpoints allow for the sample clock on USB audio devices to not
be synchronized to the USB clock. the sync endpoint gives information
on how much data to send to the data endpoint. although devices that
require sync endpoints will "work" when the sync endpoint inormation
is ignored, there is a possibility of static, echoing, or any other
type of clock desync error.
requires some small changes to existing code:
* tighten up checks for whether a setting needs/supplies a sync
endpoint. ignore settings that need a sync endpoint but don't
supply one. previously all settings that require a sync endpoint
were ignored.
* if a sync endpoint is being used, use the same denominator for
fractional samples as the sync endpoint uses (2**16).
this only implements playback sync endpoints. recording sync
endpoints are an odd concept: the driver would control the clock
rate of the device. there may be such devices, but I can't even
imagine how that could be reliably implemented. I guess you would
sync to the USB clock or the system clock ... but then, what's the
point?
|
|
|
|
Help by jmc, earlier version OK thib krw
|
|
not room. we do place them on the amd64 install media though, since many
of them matter more for 64 bit mode.
|
|
is now shared with all processes/threads. As a result, you can now use the
FPU in true process context (instead of just in kernel threads), but you
need to make sure you restore the default FPU state before calling
fpu_kernel_exit() if you change rounding mode, precision or exception masks.
Lots of discussion with thib@ and Mike Belopuhov.
ok thib@, deraadt@
|
|
ok deraadt@
|
