| Age | Commit message (Collapse) | Author |
|---|
|
supported it doesn't do any harm), so put the KNOTE() in selwakeup() itself and
remove it from any occurences where both are used, except one for kqueue itself
and one in sys_pipe.c (where the selwakeup is under a PIPE_SEL flag).
Based on a diff from tedu.
ok deraadt
|
|
fails after an escape character, and while there put explicit casts to
l1_command_build() variadic arguments.
|
|
|
|
the MAC event register.
fix from atte dot peltomaki at iki dot fi
tested by me on 5708 and 5709
|
|
|
|
- add some unknown Intel devices in dmeslog from infinst911_autol.zip
ok jsg@
|
|
so that a bridge-etherip-tunnel host can join into the bridge itself.
It is ridiculous that this capability was missing from our network
stack portfolio, considering we have bgp and ospf daemons...
discussed at length with claudio
|
|
for IP35 systems with IOC3 onboard Ethernet to get their Ethernet address
since it's no longer stored as an owmac(4) device on the IOC3 device itself.
|
|
load. This makes it possible to load bsd.rd on the RB600.
Bump version number.
ok dms@
|
|
ok miod@, dms@
|
|
cache size; might skirt some cache hazards.
ok deraadt@
|
|
attach, print it, and decide how many RX descriptors to use accordingly.
|
|
lack of such hardware.
|
|
|
|
|
|
- wakeup device earlier in read_prom
- fix ampdu_tx_start (not used yet)
- initialize ht_caps field and rx mcs set (not used yet)
- start processing compressed blockack notifications (does nothing for now)
|
|
was breaking non GNUC defining compilers.
Came up during a conversation with ragge@, positive
comments from several.
|
|
|
|
|
|
as the onboard ioc device, if one has already been found on this node.
Also, on Origin 300, do not attempt to attach the PS/2 controller on the
onboard ioc(4) since PS/2 ports are not wired.
|
|
|
|
|
|
TGT_ORIGIN, which enables support for all IP27 and IP35 systems. The original
two options have always been used together, and go back to when pefo thought
supporting multiple nodes would be significant work. Since an Origin 200
can be a dual-node system, making a distinction between single node and
multiple node systems is a moot point anyway.
Be sure to rerun config(8) before rebuilding a kernel.
|
|
system type list (which really is the system family) and a subsystem type.
No functional change yet.
|
|
|
|
anymore, as this causes the nsphy connected to the onboard iec to sometimes
disappear after a warm boot.
Unfortunately this brings back the long reboot times on Origin 200, despite
still asking for no memory test.
|
|
tested by phessler@ pyr@
ok claudio@
"go ahead" deraadt@
|
|
allocate a buffer of the right size.
ok oga@
|
|
|
|
|
|
From James Giannoules
|
|
TRY_AGAIN_LATER. NO_CCB is a timer based mechanism that can trivially
be made to fail by running IO to two or more disks simultaneously. The
TRY_AGAIN_LATER thing is more subtle because it now is a permanent
failure instead of transient however this is much harder to hit because
something must have gone wrong before it hits.
ok deraadt krw miod
|
|
from Brad
|
|
ok jsing@, miod@
|
|
|
|
never made it into production, so remove some dead code and pci ids.
inspired by a similar change to iwlwifi.
|
|
DPRINTF/DNPRINTF() debugging.
|
|
ok miod@
|
|
would stop RX operation if it had to cross a 4KB boundary during receive).
|
|
|
|
though this does nothing on i386 and amd64.
|
|
|
|
header is properly aligned; speeds up RX buffer -> mbuf copies.
|
|
everything just more complicated. Make sure the structs align nicely.
OK deraadt@
|
|
so do nothing in set_key() if the interface is not up and running.
fixes a panic reported by Steph (frlinux at gmail dot com) with
run(4) on misc
|
|
|
|
do not ignore BUS_DMA_NOCACHE (used by some variants of auich and
ati drm only).
ok kettenis
"That looks right" deraadt
|
|
tables on top of a rdomain) but until now our code was a crazy mix so that
it was impossible to correctly use rtables in that case. Additionally pf(4)
only knows about rtables and not about rdomains. This is especially bad when
tracking (possibly conflicting) states in various domains.
This diff fixes all or most of these issues. It adds a lookup function to
get the rdomain id based on a rtable id. Makes pf understand rdomains and
allows pf to move packets between rdomains (it is similar to NAT).
Because pf states now track the rdomain id as well it is necessary to modify
the pfsync wire format. So old and new systems will not sync up.
A lot of help by dlg@, tested by sthen@, jsg@ and probably more
OK dlg@, mpf@, deraadt@
|
|
blocksizes if the device doesn't support playback.
|
|
recording and playback
|
