committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
| d436d6e9 | ian | Oct. 16, 2019, 4:19 p.m. | Revert r351218 (by manu). While the changes in r351218 appear to be (and
should be) correct, they lead to the eMMC on a Beaglebone failing to work in some situations. The TI sdhci hardware is kind of strange. The first device inherently supports 1.8v and 3.3v and the abililty to switch between them, and the other two devices must be set to 1.8v in the sdhci power control register to operate correctly, but doing so actually makes them run at 3.3v (unless an external level-shifter is present in the signal path). Even the 1.8v on the first device may actually be 3.3v (or any other value), depending on what voltage is fed to the VDDS1-VDDS7 power supply pins on the am335x chip. Another strange quirk is that the convention for am335x sdhci drivers in linux and uboot and the am335x boot ROM seems to be to set the voltage in the sdhci capabilities register to 3.0v even though the actual voltage is 3.3v. Why this is done is a complete mystery to me, but it seems to be required for correct operation. If we had complete modern support for the am335x chip we could get the actual voltages from the FDT data and the regulator framework. But our am335x code currently doesn't have any regulator framework support. Reverting to the prior code will get the popular Beaglebone boards working again. This is part of the fix for PR 241301, but also requires r353651 for a complete fix. PR: 241301 Discussed with: manucgit ViewVC |
|
| 49dfdf63 | ian | Oct. 16, 2019, 4:03 p.m. | Relax the sdhci(4) check that filters out the 1.8v voltage option unless
the slot is flagged as 'embedded'. The features related to embedded and shared slots were added in v3.0 of the sdhci spec. Hardware prior to v3 sometimes supported 1.8v on non- removable devices in embedded systems, but had no way to indicate that via the standard sdhci registers (instead they use out of band metadata such as FDT data). This change adds the controller specification version to the check for whether to filter out the 1.8v selection. On older hardware, the 1.8v option is allowed to remain. On 3.0 or later it still requires the embedded-slot flag to remain. This is part of the fix for PR 241301 (eMMC not detected on Beaglebone). Changes to the sdhci_ti driver are also needed for a full fix. PR: 241301cgit ViewVC |
|
| b4efea53 | markj | Oct. 16, 2019, 3:50 p.m. | Clear PGA_WRITEABLE in moea_pvo_remove().
moea_pvo_remove() might remove the last mapping of a page, in which case it is clearly no longer writeable. This can happen via pmap_remove(), or when a CoW fault removes the last mapping of the old page. Reported and tested by: bdragon Reviewed by: alc, bdragon, kib MFC after: 1 week Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D22044cgit ViewVC |
|
| 2981bc73 | avg | Oct. 16, 2019, 3:21 p.m. | fix section number in zfs-program.8 | |
| 88f8e098 | avg | Oct. 16, 2019, 3:01 p.m. | attach itwd to the module build on x86 | |
| edca4938 | avg | Oct. 16, 2019, 2:57 p.m. | itwd(4): driver for watchdog function in ITE Super I/O chips | |
| 8338f584 | kevans | Oct. 16, 2019, 2:55 p.m. | bectl(8): destroy: use BE_DESTROY_AUTOORIGIN if -o is not specified
-o will force the origin to be destroyed unconditionally. BE_DESTROY_AUTOORIGIN, on the other hand, will only destroy the origin if it matches the format used by be_snapshot. This lets us clean up the snapshots that are clearly not user-managed (because we're creating them) while leaving user-created snapshots in place and warning that they're still around when the BE created goes away.cgit ViewVC |
|
| bc37ac7e | avg | Oct. 16, 2019, 2:46 p.m. | wbwd: move to superio(4) bus
This allows to remove a bunch of low level code. Also, superio(4) provides safer interaction with other drivers that work with Super I/O configuration registers. Tested only on PCengines APU2: superio0: <Nuvoton NCT5104D/NCT6102D/NCT6106D (rev. B+)> at port 0x2e-0x2f on isa0 wbwd0: <Nuvoton NCT6102 (0xc4/0x53) Watchdog Timer> at WDT ldn 0x08 on superio0 The watchdog output is incorrectly wired on that system and the watchdog does not really do it its job, but the pulse can be seen with a signal analyzer. Reviewed by: delphij, bcr (man page) MFC after: 19 days Differential Revision: https://reviews.freebsd.org/D21979cgit ViewVC |
|
| 455d8009 | kevans | Oct. 16, 2019, 2:43 p.m. | libbe(3): add needed bits for be_destroy to auto-destroy some origins
New BEs can be created from either an existing snapshot or an existing BE.
If an existing BE is chosen (either implicitly via 'bectl create' or
explicitly via 'bectl create -e foo bar', for instance), then bectl will
create a snapshot of the current BE or "foo" with be_snapshot, with a name
formatted like: strftime("%F-%T") and a serial added to it.
This commit adds the needed bits for libbe or consumers to determine if a
snapshot names matches one of these auto-created snapshots (with some light
validation of the date/time/serial), and also a be_destroy flag to specify
that the origin should be automatically destroyed if possible.
A future commit to bectl will specify BE_DESTROY_AUTOORIGIN by default so we
clean up the origin in the most common case, non-user-managed snapshots.
cgit
ViewVC
|
|
| e3df342a | avg | Oct. 16, 2019, 2:42 p.m. | move nctgpio to superio(4) bus
This is where it logically belongs. The change allows to drop a bunch of low lewel code. Reviewed by: gonzo MFC after: 19 days Differential Revision: https://reviews.freebsd.org/D21980cgit ViewVC |
|
| 3635891a | manu | Oct. 16, 2019, 1:53 p.m. | dwc3: Use a pair of ()'s around arguments for some macros | |
| e8709d7d | andrew | Oct. 16, 2019, 1:30 p.m. | Use tables to store the information to decode the arm64 ID registers.
Arm updates these with each new architecture revision. To help keep them updated use a collection of tables to hold the needed information to decode these registers. Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D22020cgit ViewVC |
|
| 9bb37c03 | andrew | Oct. 16, 2019, 1:21 p.m. | Stop leaking information from the kernel through timespec
The timespec struct holds a seconds value in a time_t and a nanoseconds value in a long. On most architectures these are the same size, however on 32-bit architectures other than i386 time_t is 8 bytes and long is 4 bytes. Most ABIs will then pad a struct holding an 8 byte and 4 byte value to 16 bytes with 4 bytes of padding. When copying one of these structs the compiler is free to copy the padding if it wishes. In this case the padding may contain kernel data that is then leaked to userspace. Fix this by copying the timespec elements rather than the entire struct. This doesn't affect Tier-1 architectures so no SA is expected. admbugs: 651 MFC after: 1 week Sponsored by: DARPA, AFRLcgit ViewVC |
|
| f9cb60c6 | imp | Oct. 16, 2019, 1:20 p.m. | bsd.compat.mk isn't setup to be included outside of Makefile.inc so comment it | |
| b6528d54 | avg | Oct. 16, 2019, 9:29 a.m. | MFV r353637: 10844 Serialize ZTHR operations to eliminate races
illumos/illumos-gate@6a316e1f6d32750bb8fcf2558dcb17b90ca580fd https://github.com/illumos/illumos-gate/commit/6a316e1f6d32750bb8fcf2558dcb17b90ca580fd https://www.illumos.org/issues/10844 ZoL 61c3391acc9 Serialize ZTHR operations to eliminate races Portions contributed by: Jerry Jelinek <jerry.jelinek@joyent.com> Author: Serapheim Dimitropoulos <serapheim@delphix.com> Obtained from: illumos, ZoL MFC after: 3 weekscgit ViewVC |