| Age | Commit message (Collapse) | Author |
|---|
|
and Belkin F6C120 UPS, both UQ_BAD_HID.
|
|
|
|
and Belkin F6C120 UPS.
|
|
ok deraadt@, earlier version ok jasper@, feedback halex@
|
|
to ease grepping, rewording them slightly to mostly fit onto 1 line
and to clarify UQ_EHCI_NEEDTO_DISOWN. ok deraadt@
|
|
When we move more towards kms we'll need to save/restore what is bound
to the aperture, but right now this is not needed (since we always
unbind everything before we go down anyway).
"can not hurt" deraadt@. tested by halex, deraadt and maybe some others.
|
|
- small tweak while here
|
|
tested by marco@
|
|
If this happens the imsg may no longer be usable as there may be queued
messages, but this is a) already the case with the code now, and b)
would be the case if recvmsg() fails anyway, so we can document that -1
from imsg_read() invalidates the struct imsgbuf.
discussed with and ok eric
|
|
suspend, we must roll back by calling wsdisplay_resume() or the virtual
console switching will be locked forever
ok oga
|
|
Check for emptiness of the TX queue instead of lastds != NULL.
I have a feeling this might fix the "device timeout" issues reported
by Rivo Nurges on his AR5418 unveiled by athn.c r1.28 commit, though
he is not around to confirm.
This is a candidate for -stable.
|
|
check result of carrier leakage calibration and redo calibration if needed
add support for newer AR9285 chips (AR9285 XE 2.0).
tested for non-regression on a DNXA-95
"Still seems to work here" kettenis@
|
|
to be changed before calling nexthop_delete() or the nexthop will not be
correclty removed in the unlikly event when all aspathes move to a different
nexthop while the lookup happens.
sthen@ agrees with the logic.
|
|
so don't give that impression.
ok jmc@ deraadt@ xsa@
|
|
|
|
from mlarkin@ and me, with some amd64 fixes thrown in by deraadt@
ok marco@, deraadt@, pirofti@, mlarkin@
|
|
|
|
lots of build testing by deraadt, ok/feedback deraadt guenther kettenis
|
|
Micah Cowan.
|
|
|
|
give them back again, effectively stopping and starting these CPUs. Use
the stop function in sys_reboot().
ok marco@, deraadt@
|
|
is presented for some of the Broadcom bge(4) FastE adapters. From Brad.
|
|
|
|
- make the ``-m mode'' option per subdevice, allowing
subdevices to be play-only or rec-only even if the
server is full-duplex
- add ``monitoring'' mode (with ``-m mon''). This is a
record-only stream from which played streams can be
recorded (kind of ``record what you hear'').
- allow MIDI devices to be subscribed to the controlling
MIDI port of the server, ie what midicat does (with -f
option), but using the -q option.
- add flow control to the protocol, and serialize clock
ticks (sio_onmove() calls) and data chunks. This should
fix certain full-duplex programs, broken with ``magic''
block/buffer size combinations.
- enable 3 block latency which is the minimum theoretical.
Make -z and -b options correspond to device parameters.
- make sio_getcap(3) the same for aucat and sun backends,
ie return whatever is supported (``everything'' in the
aucat case, since everything is actulally supported).
aucat (player):
- enable ``-m mode'' option to select between monitoring
and recording when ``-o file'' is used.
- plug MIDI code to non-server codepath. The MIDI control
device is specified with the ``-q device'' option, as in
server mode.
- impliment lseek()'ing within files (controlled
through MIDI). Necessary to use aucat with a MIDI
sequencer.
midicat (thrubox):
- rename ``-f'' flag to ``-q'', so it has the
same name as in aucat (-f is still working)
ok jakemsr@, tweaks from jmc@
|
|
we're using. fixes operation on some 5GHz channels (e.g 153).
great thanks to Yao Zhao (dragonlinux at gmail dot com) for
identifying the issue on run(4).
|
|
two distinct sets of routines: one for the ARCBios-compatible path used on
non-KL systems (such as O2 and Octane), and one for the KL system using
dksc() paths.
When trying to match a dksc() path, walk the KL configuration of the whole
system until the dksc controller is found; since the controller numbers are
not assigned sequentially and contiguously, the old code would not work on
complex systems (such as when booting from controller #6 when #3 to #5 are
unaffected).
|
|
and compare against them when attaching potential console drivers, to figure
out whether they indeed are acting are console devices or not.
|
|
and routines to turn a KL console and a KL component structs, respectively,
into struct sgi_device_location for further device identification.
XXX Due to the way PCI devices are numbered on PIC buses, this code is tainted
XXX by knowledge about PIC widgets, to compensate. I have considered changing
XXX xbridge(4) to have our PCI device numbering match KL on PIC-connected
XXX devices, but I expect this to be even uglier. This is not settled yet.
|
|
identify a given device by its physical connection, and add a lazy compare
routine. This will be used shortly.
|
|
instead of duplicating tedious mask and shift constructs MAXINT times.
|
|
|
|
that the radio is disabled with the same message as in other drivers.
let initialization continue for the moment until i'm sure it is correct.
|
|
|
|
Found after jbg@ sent me a horrible dmesg.
|
|
cleaned up to be less gross after some suggestions from stsp.
ok stsp@
|
|
that could be PCI-X. This bit is not valid for PCIe controllers.
From Brad
|
|
Address Autoconfiguration in IPv6". For those among us who are paranoid
about broadcasting their MAC address to the IPv6 internet.
Man page help from jmc, testing by weerd, arc4random API hints from djm.
ok deraadt, claudio
|
|
|
|
struct kroute or kroute6 pack the needed info into a struct bgpd_addr.
No flames comming out of my and sthen@'s bgpd routers.
|
|
|
|
ok jmc@ otto@
|
|
|
|
noted by damien@
|
|
ok deraadt@, damien@
|
|
|
|
|
|
ratchov, to avoid messing up his current diff...
|
|
|
|
|
|
|
