| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
- Lock the emuldata in a case when we just created it.
Sponsored by: Google SoC 2006
Submitted by: rdivacky
Suggested by: jhb
|
|
|
|
| |
Obtained from: TrustedBSD Project
|
|
|
|
|
|
|
|
| |
futex lock).
Sponsored by: Google SoC 2006
Submitted by: rdivacky
Suggested by: jhb
|
|
|
|
|
|
|
|
|
| |
it was present only in the enable path, not the disable path, which one
presumes would be equally of interest. Either way, it was not needed,
as the sysctl framework already calls suser() if the operation is a
write operation, which configuration requests are.
Sponsored by: nCircle Network Security, Inc.
|
|
|
|
|
|
|
| |
value is out of the supported range.
Noticed by: Ed Schouten <ed@fxq.nl>
Reviewed by: Kazuhito HONDA <kazuhito@ph.noda.tus.ac.jp>
|
|
|
|
|
|
| |
- remove debuging printf [2]
Submitted by: intron <mag@intron.ac> [1], rdivacky [2]
|
|
|
|
|
|
|
| |
warning isn't generated when __getcwd() is invoked.
MFC after: 3 days
Obtained from: TrustedBSD Project
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
and Jack Vogel for driver changes.
Submitted by: Jack Vogel
|
|
|
|
|
| |
Requested by: jkim
Approved by: kan (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to it. Try to co-operate with the IPMI/ASF firmware accessing the PHY.
One we get link we don't mess with the PHY. If we do then over time
the NIC will go off line. It would be nice if we could tell if IPMI
was enabled on the chip but I can't figure out a reliable way to do
that. The scheme I tried worked on a Dell PE850 but not on an HP machine.
So we assume any NIC that has ASF capability needs to deal with it.
The code was inspired by the support in Linux from kernel.org and Broadcom.
Broadcom did give me some info. but it is rather limited and is mostly
just what is in the Linux driver. Thanks to the numerous people that
helped debug the many prior versions and that I didn't break other
bge(4) HW.
Reviewed by: several people
Tested by: even more
|
|
|
|
|
|
| |
syscalls instead:
sigqueue, thr_set_name, thr_setscheduler, thr_getscheduler,
thr_setschedparam.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
it possible to e.g. distribute kernels with config names larger
than eight symbols, without the clash. Previousy, LALALALA
and LALALALA-SMP would be the same tarball. (I think this
comes from the old days where tarballs were put on the MS-DOS
formatted diskettes.)
MFC after: 3 days
|
|
|
|
|
|
|
| |
structures, in order to avoid the possibility of attempted recursive
lock acquisition for chunks_mtx.
Reported by: Slawa Olhovchenkov <slw@zxy.spb.ru>
|
|
|
|
| |
Noticed by: davidch
|
|
|
|
| |
panther is down at the moment, so better fix will follow later.
|
|
|
|
|
|
|
|
|
|
| |
given as dso handle, but also in the implicit dependencies of that dso.
Also, const-ify the read-only parameter objlist of symlook_list.
Reported by: "Simon 'corecode' Schubert" <corecode at fs ei tum de>
Approved by: kan (mentor)
X-MFC-After: 6.2
|
| |
|
|
|
|
|
|
| |
Suggested by: Milos Vyletel (mv@rulez.sk)
Reviewed by: ru
Approved by: keramida (mentor), trhodes (mentor)
|
|
|
|
| |
Reported by: andre
|
|
|
|
| |
description.
|
|
|
|
|
| |
creating a compress TIME WAIT states, if both connection endpoints
are local. Default is off.
|
| |
|
| |
|
|
|
|
|
|
| |
"make TARGET=<machine> build*", now that it actually works.
Prompted by: imp
|
|
|
|
|
|
| |
to work. Some build-tools that are part of cross-tools (cc_tools)
also need to know the proper values of TARGET_ARCH and TARGET, so
tell them.
|
|
|
|
|
|
| |
is a socialist state.
Submitted by: Shteryana Shopova <shteryana@FreeBSD.org>
|
| |
|
|
|
|
|
|
|
| |
write failure probability.
- Allow to specify an error number to return of failure.
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
| |
Remove a paragraph about over building security, it's a bit off.
Discussed with: des, FreeBSD-security
|
|
|
|
|
|
|
|
|
|
|
| |
Ever since rev 1.68 re(4) checks the validity of link in re_start.
But rlphy(4) got a garbled data due to a different bit layout used on
8139C+ and it couldn't report correct link state. To fix it, ignore
BMCR_LOOP and BMCR_ISO bits which have different meanings on 8139C+.
I think this also make dhclient(8) work on 8139C+.
Reported by: Gerrit Kuehn <gerrit AT pmp DOT uni-hannover DOT de>
Tested by: Gerrit Kuehn <gerrit AT pmp DOT uni-hannover DOT de>
|
| |
|
| |
|
|
|
|
| |
s/USBBASEDEVICE/device_t/g
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is to able to be called after *all* attach and enable events are done.
We establish a SYSINIT hook to call this handler. The current usage for it
is to add scsi target resources *after* all enables are done. There seems
to be some dependencies between different halves of a dual-port with respect
to target mode.
Put in more meaningful event messages for some events- in particular
QUEUE FULL events so we can see what the queue depth was when the
IOC sent us this message.
MFC after: 1 week
|
|
|
|
|
|
|
| |
- Add support for Intel 965 Express chipsets.
- Add support for R200 vertex programs, along with minor bugfixes.
- Add support for vblank synchronization to pipe B of Intel hardware
(laptop screens).
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
| |
unsure if this driver correctly implements all the start/stop junk
right (but it did or didn't before I made this commit).
|
|
|
|
|
| |
offsets were originally documented incorrectly. This fixes that. It
shouldn't affect anything other than error stat reporting.
|
|
|
|
|
|
|
|
|
|
| |
bthidd(8) now was integrated with vkbd(4) and supports
multiple keyboards via vkbd(4)/kbdmux(4).
The code was tested with Apple Bluetooth keyboard and
SE k700i cell phone (remote control feature).
MFC after: 1 month
|
|
|
|
|
|
|
|
| |
I found one bug. Pass our idea of TARGET_ARCH and TARGET down to
XMAKE, the cross-tools make. Previously it worked because usually
TARGET_ARCH was specified on the initial make's command line.
This should also allow us to simplify the "universe" target, which
I'm currently testing.
|
| |
|
| |
|
|
|
|
| |
events.
|
|
|
|
|
|
| |
Modified release notes: BIND 9.3.2-P1.
MFCs noted: GCC 3.4.6.
|