| Age | Commit message (Collapse) | Author |
|---|
|
with autoconf enabled.
If one is doing SLAAC one does already trust link local icmp6 so the
policy for icmp6 redirects should be the same.
pointed out by & OK bluhm@; OK henning@
|
|
|
|
takes care of.
ok dlg@
|
|
cut it out of the code to simplify things.
ok mikeb@
|
|
hardware can do (9k). implement the rxr ioctl while here.
ok jsg@
|
|
pointed out & OK bluhm@
|
|
the tree. Found by millert@.
|
|
index update code from the buf_get success path to the do it all
the time code path. Tested by millert; ok dlg, deraadt
|
|
to the vendor/make whitelist maintained by Intel so there's no
reason to start doing it now.
When syncing the driver to the FreeBSD codebase I have decided
to take this chunk as is but it appears that it breaks cheap
chinese SFP+ fiber optics modules that we all love. And while
there's still a lot of places where we check for the vendor
OUI, most of these checks are not necessary.
Issue reported and fix tested by Tony Sarendal. Thanks!
|
|
processing of router advertisements was already in the kernel.
With this rtsol{,d}(8) is no longer necessary.
The kernel starts sending solicitations with
# ifconfig $IF inet6 autoconf
or
inet6 autoconf
in /etc/hostname.$IF.
input stsp@
much help & OK mpi@
tweaks & OK bluhm@
|
|
|
|
* SIOCG80211ALLNODES operates on struct ieee80211_nodereq_all, not
struct ieee80211_nodereq.
* Six SIOC* from wi(4) were using same codes with generic parts of
IEEE 802.11 framework. Things worked due to the fact that size
of data struct being passed is encoded in actual SIOC*, too.
This commit means that ifconfig and some ports will need to be rebuilt,
if any of affected SIOC* codes is used. Port bumps to follow.
First part okay reyk@, whole diff okay mpi@
Heavy prodding to commit now from deraadt@
|
|
|
|
|
|
need it.
OK mpi@
|
|
decl definition from somewhere in .h. This appears to be the only fallout
in the kernel.
|
|
So add the types blksize_t (a.k.a. int32_t) and blkcnt_t (a.k.a.
int64_t). Use blkcnt_t in stat.h since the base type (int64_t) does
not change. blksize_t in stat.h will follow after the tree is audited
for signed issues, since the base type will change from u_int32_t
to a POSIX compliant int32_t.
Guidance and feedback from guenther@
ok millert@
|
|
|
|
With this change sensorsd(8) now correctly detects state changes when
docking and undocking.
ok mlarkin@
|
|
a driver does not implement a specific *_activate() handler and that our
USB stack sets the dying flag before detaching a device, these specific
handlers can die.
|
|
to use BGE_STD_RX_RING_CNT instead of BGE_JUMBO_RX_RING_CNT.
ok dlg@
|
|
|
|
|
|
invalid. When such thing happens, it means that the address is no
longer configured on the system but still referenced by some routes.
So do not return such ifa in ifa_ifwithroute().
Fix a panic reported by Pierre Bardou.
ok mikeb@, henning@
|
|
fields.
found by steven roberts, who also tested this fix for me
|
|
|
|
Izumi Tsutsui, thanks!
ok miod@
|
|
The interface has been disabled by default for about 4 years and
currently there's not much value in having it around at all.
ok deraadt
|
|
The interface has been disabled by default for about 4 years and
currently there's not much value in having it around at all.
ok deraadt
|
|
device tables and kernel config files. ok deraadt
|
|
ok guenther@
|
|
them up and the others i found in this file.
no functional change.
|
|
putting this into the tree to make it easier to test.
|
|
putting this in the tree to make it easier for people to test.
|
|
putting this in the tree to make it easier for people to test.
|
|
the right shape now, we dont have to do it by hand all over the place
any more.
rework the rxr ring management to use if_rxring while here.
largely based on if_sk.c r1.152 and if_skvar.h r1.4 by kettenis.
tested by me on:
skc0 at pci3 dev 11 function 0 "Schneider & Koch SK-98xx" rev 0x12, GEnesis (0x0): apic 3 int 5
sk0 at skc0 port A: address 00:00:5a:99:8a:ec
xmphy0 at sk0 phy 0: XMAC II Gigabit PHY, rev. 2
and this from ian mcwilliam
skc0 at pci0 dev 9 function 0 "D-Link DGE-530T B1" rev 0x11, Yukon Lite (0x9): apic 2 int 17
sk0 at skc0 port A: address 00:17:9a:ba:b5:39
eephy0 at sk0 phy 0: 88E1011 Gigabit PHY, rev. 5
tested by brad@ too
|
|
add an explicit rwlock around the global state (the pool list and serial
number) rather than rely on implicit process exclusion, splhigh and splvm.
the only things touching the global state come from process context so we
can get away with an rwlock instead of a mutex. thankfully.
ok matthew@
|
|
interrupts in PIC rev 1; from IRIX via Linux 2.5.69.
This doesn't fix the lost SCSI interrupts jasper@ eventually experiences on
Origin 350 systems, but this can't hurt anyway.
|
|
No change but ordering in the generated files, so I won't even bother to
regen them - this is only a `documentation' change.
|
|
|
|
Shuffle the code around slightly, so we special case the 5209 chipset
instead of semi-randomly.
Tested on rts5227 by me, and rts5209 by stsp@
OK stsp@
|
|
|
|
also adds a broadcast entry flagged with RTF_BROADCAST.
Prior to this change broadcast entries were simple clonned ARP entries,
that would be deleted once their timer expired since they would always
be incomplete.
With this change they are now persistant and identifiable with a new flag.
Committing early to be able to deal with any potential fallout before we
start relying on this.
ok florian@, mikeb@, henning@
|
|
|
|
When pms(4) is attached to a touchpad it generally presents two different
wsmouse(4) devices: one for the touchpad itself and one for the clitpad
and/or some interleaved packets. But since both devices are writing to
the same pckbc slot, a race can occur if they try to change the state at
the same time.
So prevent two process opening the two /dev/wsmouse* node at the same time
to corrupt the magic sequences needed to enable/disable the touchpad.
ok schadchin@
|
|
while (space) {
IFQ_POLL;
myx_dequeue(free descr);
IFQ_DEQUEUE;
etc;
}
with
while (space && myx_dequeue(free descr)) {
IFQ_DEQUEUE;
etc;
}
|
|
Those two functions take one dev_t argument, not int. Match declarations
with reality. No functional changes.
|
|
|
|
depend upon the address being at the beginning of a cache line, for we may
arrive in the middle of a line thanks to a branch. Noticed the hard way...
|
|
|
