| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
something: offset into the first mbuf of the target chain before copying
the source data over.
Make drivers using m_devget() with a first argument "data - ETHER_ALIGN"
to use the offset argument to pass ETHER_ALIGN in. The way it was previously
done is potentially dangerous if the source data was at the top of a page
and the offset caused the previous page to be copied (if the
previous page has not yet been appropriately mapped).
The old `offset' argument in m_devget() is not used anywhere (it's always
0) and dates back to ~1995 (and earlier?) when support for ethernet trailers
existed. With that support gone, it was merely collecting dust.
Tested on alpha by: jlemon
Partially submitted by: jlemon
Reviewed by: jlemon
MFC after: 3 weeks
|
| |
|
|
|
|
|
|
| |
one.
Pointy-hat to: me
|
|
|
|
|
|
|
|
| |
into FreeBSD.
PR: kern/23620
Submitted by: rh@matriplex.com
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the console device was open. At other times, the interrupts that
are used to detect the break signal or ~^B sequence were disabled,
so these events would not be noticed until the next open (e.g. the
next kernel printf). This was mainly a problem while there was no
getty running on the console, such as during bootup or shutdown.
For serial consoles with break-to-debugger support, we now enable
the generation of interrupts at attach time, and we leave them
enabled while the device is closed.
Reviewed by: bde (I've since made chages as per his suggestions)
|
| |
|
| |
|
|
|
|
|
| |
o For the -i switch, only show the device if more than one is given on
the command line.
|
|
|
|
|
|
|
|
|
|
|
| |
via the new DIGIIO_SETALTPIN ioctl, and allow the port's ALTPIN setting
to be queried via DIGIIO_GETALTPIN.
The initial state and lock devices are normally used to set and/or
lock ALTPIN settings although the device itself may also be used.
ALTPIN settings are applied per-device and apply to both the callin
and callout device at the same time.
|
| |
|
|
|
|
|
|
| |
of alternate source trees.
Also improve verbose behaviour.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the following description in RFC2461:
AdvSendAdvertisements
A flag indicating whether or not the router sends
periodic Router Advertisements and responds to
Router Solicitations.
Default: FALSE
Note that AdvSendAdvertisements MUST be FALSE by
default so that a node will not accidentally start
acting as a router unless it is explicitly
configured by system management to send Router
Advertisements.
Submitted by: JINMEI Tatuya <jinmei@isl.rdc.toshiba.co.jp>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
sizeof(ro_dst) is not necessarily the correct one.
this change would also fix the recent path MTU discovery problem for the
destination of an incoming TCP connection.
Submitted by: JINMEI Tatuya <jinmei@kame.net>
Obtained from: KAME
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
of tunclose() rather than the end, and tunopen() grabbed that unit
before tunclose() finished (one process is allocating it while another
is freeing it!).
It may be worth hanging some sort of rw mutex around all specinfo
calls where d_close and the detach handler get a write lock and all
other functions get a read lock. This would guarantee certain levels
of ``atomicity'' (is that a word?) that people may expect (I believe
Solaris does something like this).
|
|
|
|
|
|
|
|
|
|
| |
exist, and therefore mm_install is returning the "fail" value of
the test instead of the "success" value for install.
This change is a no-op on HEAD, but since the only harm on RELENG_4
ATM is a spurious warning it can follow the usual MFC practice.
Submitted by: A cast of thousands :-/
|
| |
|
|
|
|
|
|
|
| |
TI1210, TI4410 and TI4450
and fix what looks like a typo in the OZ6860 entry.
Obtained from: NetBSD
|
|
|
|
|
| |
Reviewed by: ru
MFC after: 2 weeks
|
|
|
|
| |
them yet)
|
|
|
|
|
| |
PR: misc/28283
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Submitted by: Oliver Fromme <oliver.fromme@heim3.tu-clausthal.de>
|
|
|
|
|
| |
now. The proc locking isn't actually safe yet and won't be until the proc
locking is finished.
|
| |
|
|
|
|
| |
Submitted by: ru
|
|
|
|
|
|
|
| |
discards qualifier"), and probably adds a few where module names are
compared to or passed as non-const strings.
Not-objected-to-by: bde
|
|
|
|
|
| |
To use a FAITH actually, you also need faithd(8) setup.
Please consult faithd(8) manpage.
|
|
|
|
|
|
|
|
|
|
| |
columns confuse the heck out of other apps trying to parse vmstat output
(eg sscope). I made sure we're still <= 80 cols per line.
Fixed warnings about unused vars and printf %format mismatches.
Requested by: Eugene Aleynikov <eugenea@infospace.com>
Reviewed by: joerg (implicitly)
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
| |
Submitted by: Alexey V. Neyman <avn@any.ru>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
requirements(RFC1573, interface MIB). This change for 4.4BSD was
first introduced in if_ethersubr.c:1.17->1.18.
BTW, iflastchange on all of IFs are inconsistent. e.g.
ether, tun: update
fddi, tokenring, ppp: not update
I'll make patch later.
Obtained from: KAME
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
Obtained from: KAME
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
versions/revisions.
Modified from the original patch to mark G3 and G4 processors as such.
Submitted by: Jeff Schottmiller <jeff@neoscale.com>
|
| |
|
|
|
|
|
|
| |
This should make dependencies at load time work like before. Oops.
Noticed by: markm
|
| |
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
| |
| |
| |
| |
| |
| |
| |
| | |
* src/roff/troff/node.h (node::node): Initialize `last'.
This fixes coredump on \b'\(sq' sequence.
Urged by: eivind
|
| | |
|
| |
| |
| |
| |
| | |
PR: 28251
Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su>
|
| |
| |
| |
| |
| | |
PR: bin/4949
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| | |
PR: bin/14255
Reviewed by: Kenji Tomita <tommy@ti.com>
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- spaces -> tabs
- return(0) -> return (0)
- wrap longlines
Reviewed by: md5
MFC after: 2 weeks
|
| | |
|
| |
| |
| |
| | |
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| | |
period; this keeps the number of whitespace-separated fields constant.
PR: 15739, 23908
Submitted by: Valentin Nechayev <netch@netch.kiev.ua>
|
| |
| |
| |
| |
| |
| |
| | |
years; remove them from CFLAGS.
PR: 23712
Submitted by: Volker Stolz <stolz@i2.informatik.rwth-aachen.de>
|
| | |
|