committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r336138||ian||July 9, 2018, 7 p.m.||Add pnp info to the imx_spi driver.|
|r336137||ian||July 9, 2018, 7 p.m.||Add a manpage for the imx_spi driver.|
|r336136||imp||July 9, 2018, 6:02 p.m.||Remove gateworks nanobsd support.
A quick test of this shows multiple problems. Rather than fix the problems, just retire this board's support. It's for a 12 year old board that's been out of production for at least 7 years and generally lacks the memory to run even a stripped down NanoBSD image well. It's not really relevant anymore.ViewVC
|r336135||imp||July 9, 2018, 6:02 p.m.||Remove armeb from the list of architectures we build for the boot
laoder testing scripts. It just adds to the build time, and will be retired soon anyway, per discussions in freebsd-arch@ last month.ViewVC
|r336134||ian||July 9, 2018, 2:18 p.m.||Add missing generated header file.|
|r336132||ae||July 9, 2018, 11:35 a.m.||Add "record-state", "set-limit" and "defer-action" rule options to ipfw.
"record-state" is similar to "keep-state", but it doesn't produce implicit O_PROBE_STATE opcode in a rule. "set-limit" is like "limit", but it has the same feature as "record-state", it is single opcode without implicit O_PROBE_STATE opcode. "defer-action" is targeted to be used with dynamic states. When rule with this opcode is matched, the rule's action will not be executed, instead dynamic state will be created. And when this state will be matched by "check-state", then rule action will be executed. This allows create a more complicated rulesets. Submitted by: lev MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D1776ViewVC
|r336131||ae||July 9, 2018, 11:03 a.m.||Deduplicate the code.|
|r336130||wma||July 9, 2018, 9 a.m.||ARM64: Add quirk mechanism to pci_host_generic_acpi|
|r336129||wma||July 9, 2018, 8:55 a.m.||ARM64: Add support for ThunderX2 PCIe|
|r336128||wma||July 9, 2018, 8:41 a.m.||ARM64: Add ThunderX2 CPU revision macro. Add ThunderX2 name in identcpu.c|
|r336127||cem||July 9, 2018, 8:37 a.m.||gzip(1): Don't shadow global 'err'
Unbreak work build on ppc due to -Werror=shadow. Introduced in r336121. X-MFC-With: r336121ViewVC
|r336126||cem||July 9, 2018, 8:19 a.m.||Integrate SHA2-224 with userspace components
The double compilation of the kernel sources in libmd and libcrypt is baffling, but add yet another define hack to prevent duplicate symbols. Add documentation and SHA2-224 test cases to libmd. Integrate with the md5(1) command, document, and add more test cases; self-tests pass.ViewVC
|r336125||cem||July 9, 2018, 7:28 a.m.||OCF: Add plain hash modes
In part, to support OpenSSL's use of cryptodev, which puts the HMAC pieces in software and only offloads the raw hash primitive. The following cryptodev identifiers are added: * CRYPTO_RIPEMD160 (not hooked up) * CRYPTO_SHA2_224 * CRYPTO_SHA2_256 * CRYPTO_SHA2_384 * CRYPTO_SHA2_512 The plain SHA1 and 2 hashes are plumbed through cryptodev (feels like there is a lot of redundancy here...) and cryptosoft. This adds new auth_hash implementations for the plain hashes, as well as SHA1 (which had a cryptodev.h identifier, but no implementation). Add plain SHA 1 and 2 hash tests to the cryptocheck tool. Motivation stems from John Baldwin's earlier OCF email, https://lists.freebsd.org/pipermail/freebsd-arch/2018-January/018835.html .ViewVC
|r336124||cem||July 9, 2018, 7:26 a.m.||OCF: Add CRYPTO_SHA2_224_HMAC mode
Round out the complete set of basic SHA2 HMAC modes with SHA2-224. Support is added to the cryptocheck test tool.ViewVC
|r336123||cem||July 9, 2018, 7:24 a.m.||Implement SHA2-224 submode of SHA2-256
Like SHA2-384:SHA2-512, SHA2-224 is simply a truncated SHA2-256 with a different initial vector. Add to round out the complete basic SHA2 family.ViewVC