| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
This ensures that any ccbs which immediately start during the call to
xpt_release_devq see an accurate picture of the frozen_lun_mask.
Sponsored by: Intel
MFC after: 3 days
|
|
|
|
| |
Reported by: mjg
|
|
|
|
|
|
|
| |
- if not on a tty prompt about the missing pkg(8) but default on 'no' except if
ASSUME_ALWAYS_YES is set
MFC after: 2 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DFS parameters fetched from the HAL.
Check whether the specific chipset supports RADAR reporting before
enabling DFS; or some of the (unset) DFS methods may fail.
Tested:
* AR5210 (correctly didn't enable radar PHY reporting)
* AR5212 (correctly enabled radar PHY reporting w/ the correct default
parameters.)
TODO:
* Now that I have this capability check in place, I could remove the
(empty) DFS methods from AR5210/AR5211.
* Test on AR5416, AR9160, AR9280.
PR: kern/170904
|
|
|
|
|
|
| |
fetching the current DFS configuration.
PR: kern/170904
|
|
|
|
| |
PR: kern/170904
|
|
|
|
|
|
|
|
|
| |
variable when determining various sizes related to SCSI UNMAP block
descriptor lists.
Sponsored by: Intel
Reviewed by: mav
MFC after: 3 days
|
|
|
|
|
|
| |
as there are warnings.
Reviewed by: nwhitehorn
|
| |
|
| |
|
|
|
|
|
|
| |
I need to check whether new parameters were added for the AR5413 NIC.
PR: kern/170904
|
|
|
|
|
|
|
|
|
|
| |
internal knowledge that "cd" is a shell's built-in. Such makes
may attempt to exec() "cd" that in turn will fail on systems that
lack the "cd" executable.
Reworked this by eliminating the root cause.
Submitted by: Simon Gerraty <sjg@juniper.net>
|
|
|
|
|
|
|
| |
The only chip this is currently implemented for is the AR5416 HAL family.
A follow-up commit will add AR5212 support.
PR: kern/170904
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
| |
|
| |
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* mfp support;
* 4.9ghz support in the HAL;
* device type - specifically, the bus type and whether it's a HB63
NIC (which requires some subtle chainmask handling differences
in the AR5416 HAL.)
Obtained from: Qualcomm Atheros
|
|
|
|
| |
bridges do.
|
|
|
|
|
| |
PR: 170931
Approved by: adrian
|
|
|
|
|
|
| |
tunables.
MFC after: 1 month
|
|
|
|
| |
Submitted by: Ian Lapore (indirectly in a larger patch)
|
|
|
|
|
|
|
|
|
|
| |
Support appending to empty archives
References:
https://github.com/libarchive/libarchive/pull/17
Submitted by: myself
Obtained from: libarchive master branch on github
|
|
|
|
|
|
|
|
| |
and null-terminated at the same time, because they're later passed to
libjail as null-terminated. That means I also need to add a nul byte when
comma-combining array parameters.
MFC after: 6 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
3086 unnecessarily setting DS_FLAG_INCONSISTENT on async destroyed datasets
3090 vdev_reopen() during reguid causes vdev to be treated as corrupt
3102 vdev_uberblock_load() and vdev_validate() may read the wrong label
Referenes:
https://www.illumos.org/issues/3086
https://www.illumos.org/issues/3090
https://www.illumos.org/issues/3102
PR: kern/170912, kern/170914
Obtained from: illumos (changeset #13776, #13777)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
Merge existing attributes before processing pragmas in friend template
declarations.
Fixes pr13662.
This should help when building Firefox with libc++.
|
|
|
|
|
|
| |
workaround for it in jemalloc_FreeBSD.h.
Reviewed by: jasone
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
functional changes.
MFC after: 3 days
|
|
|
|
|
|
| |
since this determines parts of the C++ include path.
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
Bug was introduced in r192025.
Approved by: kib (mentor)
|
|
|
|
| |
in init_private(), don't call it again in fork() wrapper.
|
|
|
|
|
|
| |
Report errors indicated by the transport. If this is too chatty, I'll
throw it behind a debug write.
Remove commented out debugs that are no longer useful.
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
|
|
|
| |
Obtained from: Qualcomm Atheros
|
|
|
|
| |
Obtained from: Device IDs are from Qualcomm Atheros
|
| |
|
|
|
|
|
|
|
|
| |
properly parsed for interface prefixes and netmask suffixes. This was
already done for the old-style (fixed) command line, but missed for
the new-style.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
Remove a bogus null terminator when stripping the netmask from
IP addresses. This was causing later addresses in a comma-separated
string to disappear.
Use memcpy instead of strcpy. This could just cause Bad Things.
PR: 170832
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
| |
r128060 for "hardware-supplied entropy" reversed this without reason,
seems a typo.
* Isolate "better than nothing" implementation to a function.
Submitted by: obrien & Arthur Mesh <arthurmesh@gmail.com>
Sponsored by: Juniper Networks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUS_DMA_COHERENT attribute
The minimum unit for changing "cachable" attribute is page, so call
to pmap_change_attr effectively disable cache for all pages that newly
allocated DMA memory region spans on. The problem is that general-purpose
memory could reside on these pages too and disabling cache might affect
performance. Moreover ldrex/strex operators raise Data Abort exception
when accessing memory on page with "cachable" attribute off.
BUS_DMA_COHERENT does nto require memory to be coherent. It just suggests
to do best effort for reducing synchronization overhead.
|