| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Merge M_NOWAIT/M_DONTWAIT into a single flag M_NOWAIT.
|
|
|
|
| |
especially in troff files.
|
|
|
|
|
|
|
|
|
|
|
|
| |
o on input don't strip the Ethernet header from packets
o input packet handling is now done with if_input
o track changes to ether_ifattach/ether_ifdetach API
o track changes to bpf tapping
o call ether_ioctl for default handling of ioctl's
o use constants from net/ethernet.h where possible
Reviewed by: many
Approved by: re
|
|
|
|
| |
as per current practice.
|
|
|
|
| |
Found by: FlexeLint.
|
|
|
|
|
|
| |
this case, ugly macros, but the data tables can be reused:
Put one copy of the software HDLC tables in its own file.
|
|
|
|
|
|
| |
It seems counter-intuitive that all drivers have to do this.
Pointed in right direction by: gj
|
|
|
|
|
|
|
|
| |
i4bq931, i4b, isic, iwic, ifpi, ifpi2, ifpnp, ihfc, and itjc are
no longer count devices. Also remove a few other instances of N<DEVICE>
being used to control compilation of whole files.
Reviewed by: hm
|
| |
|
| |
|
|
|
|
|
|
|
| |
by looking at the "type of number" field and providing configurable hooks
to correct the numbers accordingly. See keywords add-prefix, prefix-national
and prefix-international in isdnd.rc(5).
This feature was implemented by Christian Ullrich <chris@chrullrich.de>
|
|
|
|
|
| |
based on patches received from Guy Ellis (guy@traverse.com.au),
Chris Collins (xfire@xware.cx) and Phillip Musumeci (phillip@cs.jcu.edu.au).
|
|
|
|
| |
Approved by: hm
|
|
|
|
|
| |
Spotted and suggested by: des
MFC after: 3 weeks
|
|
|
|
| |
ng_parse_struct_info -> ng_parse_struct_field change.
|
|
|
|
| |
disabled for gcc-3.
|
| |
|
|
|
|
| |
still, but they are due due to some bogosity in netgraph.
|
|
|
|
|
|
| |
This should be in 4.6.
Submitted by: Ari Suutari <ari.suutari@syncrontech.com>
|
|
|
|
|
|
| |
of the driver should be emitted.
This was already changed in the code committed to RELENG_4.
|
|
|
|
|
|
| |
interrupts in a loop.
Tested by: Andrew Gordon <arg-bsd@arg1.demon.co.uk>
|
|
|
|
|
|
|
| |
most cases NULL is passed, but in some cases such as network driver locks
(which use the MTX_NETWORK_LOCK macro) and UMA zone locks, a name is used.
Tested on: i386, alpha, sparc64
|
|
|
|
|
|
|
|
|
|
|
|
| |
general cleanup of the API. The entire API now consists of two functions
similar to the pre-KSE API. The suser() function takes a thread pointer
as its only argument. The td_ucred member of this thread must be valid
so the only valid thread pointers are curthread and a few kernel threads
such as thread0. The suser_cred() function takes a pointer to a struct
ucred as its first argument and an integer flag as its second argument.
The flag is currently only used for the PRISON_ROOT flag.
Discussed on: smp@
|
|
|
|
| |
Submitted by: Steven Looman <fsteevie@wish.net>
|
| |
|
|
|
|
|
| |
OpenBSD and BSD/OS and respective code, remove pre $FreeBSD CVS id's,
remove #if(def)s and respective code for FreeBSD versions < 5 .
|
|
|
|
| |
is IMHO likely not to happen anymore ...
|
| |
|
| |
|
|
|
|
| |
fatal error.
|
|
|
|
|
|
|
|
|
|
| |
which was causing the link of the kernel to fail. Since layer4/i4b_l4mgmt.c
is always required by i4b and layer3/i4b_q931.c is only needed when a
passive card is present it makes sense to have the declaration in the
former file only.
No MFC required since the problem only became apparent after a change to
the compile options in -current which AFAIK wasn't made in -stable.
|
|
|
|
|
|
|
| |
form L0IFPI2UNIT. This could result in a panic if the user tried to
trace using isdntrace(8). I fixed this locally but forgot to commit it.
Reminded by: "Wittig, Christoph" <wc@medianet-world.de>
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
net/if_spppsubr.c has all its features.
Hooray, it's gone!
MFC after: 1 month
|
|
|
|
|
|
|
| |
reported panic.
Submitted by: Alexander Leidinger <Alexander@Leidinger.net> (partly)
MFC after: 4 weeks
|
|
|
|
|
|
|
| |
were installed.
For the ifpi2, change the string in the driver_t from "ifpi2" to
"ifpi2-" so that one sees "ifpi2-0" instead of "ifpi20" at boot time.
|
|
|
|
| |
MFC after: 4 weeks
|
|
|
|
| |
MFC after: 4 weeks
|
|
|
|
| |
also don't use ANSI string concatenation.
|
| |
|
|
|
|
|
| |
in the probe routine.
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
card.
Submitted by: Steve Looman
Reviewed by: hm
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
lengths for CONNECT_REQ and CONNECT_IND are incorrect, which causes
dialouts to fail after certain error situations (an invalid -- not
wrong! -- number has been dialed). Since these messages are tagged as
too short, the device reads trailing garbage as the B protocol
parameters; this is OK as long as the garbage consists of zero bytes,
which it usually does, except after the said error.
Another change we have taken into use is to send an explicit Q.850
"normal call clearing" code when a call is ignored using PRI equipment
(specifically AVM T1); the CAPI pseudo-code for ignore, 1, translates
into something at least Ericsson exchanges interpret oddly (message
"this area is not reachable from your number"). NCCLR makes the exchange
give a busy signal, which is the behaviour at least we prefer
(conceivably, the ignore code could be made a sysctl variable).
The attached patch corrects the message length issue. It also includes a
somewhat unpretty solution for the PRI ignore code (if device's number
of channels equals 30, assume PRI and send NCCLR, otherwise send CAPI
ignore). Tested using AVM B1 PCI and T1 PCI.
Submitted by: Juha-Matti Liukkonen <jml@cubical.fi>
Reviewed by: hm
MFC after: 1 month
|
|
|
|
| |
MFC after: 2 months
|
|
|
|
|
|
|
| |
address is looked up via a hash table. Add a hack to move the entry to
a new hash bucket when the address changes.
Submitted by: tmm
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note ALL MODULES MUST BE RECOMPILED
make the kernel aware that there are smaller units of scheduling than the
process. (but only allow one thread per process at this time).
This is functionally equivalent to teh previousl -current except
that there is a thread associated with each process.
Sorry john! (your next MFC will be a doosie!)
Reviewed by: peter@freebsd.org, dillon@freebsd.org
X-MFC after: ha ha ha ha
|
|
|
|
|
|
|
|
| |
arguments to some functions.
Obtained from: NetBSD
Reviewed by: peter
MFC after: 2 weeks
|
| |
|
| |
|