| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
with clang:
sys/dev/ce/tau32-ddk.c:1228:37: warning: implicit truncation from 'int' to bitfield changes value from 65532 to 8188 [-Wconstant-conversion]
Since this file is obfuscated C, we can never determine (in a sane way,
at least :) if this points to a real problem or not. The driver has
been in the tree for more than five years, so it most likely isn't.
MFC after: 1 week
|
| |
| |
| |
| |
| | |
Reviewed by: rwatson
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
asychronous task. This avoids tearing down multicast state including
sending IGMP leave messages and reprogramming MAC filters while holding
the per-protocol global pcbinfo lock that is used in the receive path of
packet processing.
Reviewed by: rwatson
MFC after: 1 month
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While I'm here update if_oerrors if parent interface of vlan is not
up and running. Previously it updated collision counter and it was
confusing to interprete it.
PR: kern/163478
Reviewed by: glebius, jhb
Tested by: Joe Holden < lists <> rewt dot org dot uk >
|
| |
| |
| |
| |
| |
| |
| |
| | |
the INET6 code. This includes retiring the 'ndpr_next' and 'pfr_next'
macros.
Submitted by: pluknet (earlier version)
Reviewed by: pluknet
|
| |
| |
| |
| |
| |
| |
| |
| | |
using jkim's last patch (reviewed by bde) from here:
http://docs.freebsd.org/cgi/mid.cgi?201010141558.03154.jkim
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| | |
special-case optimizations on several platforms and is preferred.
Reported by: dim (indirectly)
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
decoded ranges. Pass any request for a specific range that fails because
it is not in a decoded range for an ACPI Host-PCI bridge up to the parent
to see if it can still be allocated. This is based on the assumption that
many BIOSes are inconsistent/broken and that settings programmed into BARs
or resources assigned to other built-in components are more trustworthy than
the list of decoded resource ranges in _CRS. This effectively limits the
decoded ranges to only being used for "wildcard" ranges when allocating
fresh resources for a BAR, etc. At some point I would like to only be
this permissive during an early scan of firmware-assigned resources during
boot and to be strict about all later allocations, but that isn't viable
currently.
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
at SCHED_PRI_RANGE to prevent overflows in the priority value. This can
happen due to irregularities with clock interrupts under certain
virtualization environments.
Tested by: Larry Rosenman ler lerctr org
MFC after: 2 weeks
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
kern_posix_fadvise().
Reviewed by: silence on emulation@
MFC after: 2 weeks
|
| |
| |
| |
| | |
MFC after: 3 days
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Even though _Static_assert() is pretty robust for C code, it cannot work
correctly with C++ code. This is due to the fact that C++ template
parameters may contain commas that are not enclosed in parentheses. For
example:
static_assert(foo<int, int>::bar == baz, "...");
This causes _Static_assert to be called with an excessive number of
parameters. If you want to use static_assert in C++, just use a C++11
compiler.
Reported on: current@, ports@
|
| | |
|
| |
| |
| |
| | |
Inspired by PR docs/11596.
|
| |
| |
| |
| | |
MFC after: 1 week
|
| |
| |
| |
| | |
Approved by: des (mentor)
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
bits.
The ROUERSTATION and RSPRO variants contain:
* the board specific bits (eg the RTC for RSPRO, later on it'll
include the GPIO/LED definitions);
* the boot specific bits (eg, on-board flash, usb flash, etc).
For now the AR71XX_BASE file contains the common board config,
drivers and net80211/ath wireless drivers.
I'll follow this up with config files for the other boards I
have (eg the Ubiquiti LSSR71, as well as some Mikrotik boards
that use the AR71XX and atheros reference boards) which will
be quite easy to do now.
|
| | |
|
| |
| |
| |
| |
| |
| | |
This improves performance for globs where a slash or another component
follows a component with metacharacters by eliminating unnecessary attempts
to open directories that are not.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
driver. This driver works for FreeBSD/i386 and FreeBSD/amd64 platforms.
Many thanks to HighPoint for providing this driver.
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| | |
no reason why it should be limited to 64K of DFLTPHYS. DMA data tag is any
way set to allow MAXPHYS, S/G lists (chain elements) are sufficient and
overflows are also handled. On my tests even 1MB I/Os are working fine.
Reviewed by: ken@
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Francois de La Rochefoucauld introduced in r228909 [1],[2]
2. Change c-cedilla introduced in the same commit to ASCII c since
non-UTF-8 terminals will choke on the non-ASCII text. [2],[3]
Pointed out by: bf [1]
Reviewed by: French-speakers on #bsdcode [2]
Requested by: uqs [3]
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is not necessary: errors are already caught in evalbackcmd() and
forcelocal handles changes to variables.
Note that this depends on r223024.
MFC after: 4 weeks
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
If the page lock acquisition is retried, then the underlying thread is
not unpinned.
Wrap nearby lines that exceed 80 columns.
|
| | |
|
| |
| |
| |
| | |
Approved by: des (mentor)
|
| |
| |
| |
| |
| |
| |
| | |
< nsock, not >.
Pointy hat to: cognet
Submitted by: Olivier Cochard-Labbe <olivier AT cochard doT me>
|
| |
| |
| |
| |
| | |
The details of the fix can be found in the tcpdump git repository:
commit 684955d58611ee94eccdc34e82b32e676337188c
|
| |
| |
| |
| | |
hardcoded but will be changed later with more flexible way to define them.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
P_tmpdir [OB XSI] Default directory prefix for tempnam().
This macro is used in a lot of places in legacy applications,
and is why we see a lot of programs written for e.g. Linux
store volatile temporary files in /var/tmp and not /tmp.
MFC after: 2 months
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
paravirtualized pmap implementations for i386. This includes some
style fixes to the native pmap and several bug fixes that were not
previously applied to the paravirtualized pmap.
Tested by: sbruno
MFC after: 3 weeks
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The built-in atomic operations are not implemented in our version of GCC
4.2 for the ARM and MIPS architectures. Instead of emitting locked
instructions, they generate calls to functions that can be implemented
in the C runtime.
Only implement the atomic operations that are used by <stdatomic.h> for
datatype sizes that are supported by atomic(9). This means that on these
architectures, we can only use atomic operations on 32-bits and 64-bits
variables, which is typically sufficient.
This makes <stdatomic.h> work on all architectures except MIPS, since
MIPS and SPARC64 still use libgcc. Converting these architectures to
libcompiler_rt is on my todo list.
|
| |
| |
| |
| |
| |
| | |
migrating code to C++11 easier).
Approved by: dim (mentor)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- use warnx() to tell the user whether a process is running in normal,
idle or realtime priority. with the old code it would have been possible
for another process to send data to stdout between
printf("%s: ", p);
and
printf("* priority\n");
and thus break the formatting.
- 'rtprio 10 -0' triggeres non-intuitive behavior. It would first set the
priority of itself to 10 *and* would then try to execute '-0'. Of course,
setting the priority of [id|rt]prio itself doesn't make a lot of sense,
but it is intuitive compared to the previous behavior.
- 'rtprio -t --1' will actually pass over the '-1' to rtprio(). Now
invoking rtprio like this will catch the wrong usage before passing
over the invalid argument to rtprio().
- Garrett Cooper suggested to add further diagnostics where the failure
occures, if execvp fails.
PR: bin/154042
Submitted by: arundel
MFC after: 1 month
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In an example of boot command:
- rename wd(4) IDE disk drives name to ad(4) for the time being.
- update the used kernel path "/kernel" to the current default.
[It still worked occasionally by looking into the /boot/kernel directory,
so the resulting path was "/boot//kernel/kernel", with two slashes.]
Bump .Dd for this and previous changes.
MFC after: 1 week
|
| |
| |
| |
| |
| |
| | |
in the sense data structures.
MFC after: 1 week
|
| |
| |
| |
| | |
While sorting the MLINKS by name, I forgot to re-add it.
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Vendor has integrated most of our local changes in revisions 3976-3979 so
future updates are going to be easier.
Thanks to Tim Kientzle <kientzle@FreeBSD.org>.
MFC after: 8 days
|
| | |
| | |
| | |
| | | |
Obtained from: http://libarchive.googlecode.com/svn/release/2.8
|
| | |
| | |
| | |
| | | |
Obtained from: http://libarchive.googlecode.com/svn/release/2.8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
well as provide documentation for rtprio_thread(2) system call.
MFC after: 1 month
X-MFC-after: r228470
|