#
88148a07 |
| 22-Jan-2019 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r343202 through r343319.
|
#
4945f79a |
| 20-Jan-2019 |
Andriy Voskoboinyk <avos@FreeBSD.org> |
Remove IEEE80211_AMPDU_AGE config option.
It is noop since r297774.
|
#
b9e0c8c2 |
| 12-Dec-2018 |
Maxim Sobolev <sobomax@FreeBSD.org> |
Add NETGRAPH_CHECKSUM.
MFC after: 1 week
|
Revision tags: release/12.0.0 |
|
#
24b6d871 |
| 26-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Redo r339563: Remove joy(4) driver.
This driver was marked as gone in 12. We're at 13 now. Remove it. Data from nycbug's dmesg cache shows only one potential user, suggesting it never was used much.
Redo r339563: Remove joy(4) driver.
This driver was marked as gone in 12. We're at 13 now. Remove it. Data from nycbug's dmesg cache shows only one potential user, suggesting it never was used much. However, even though this device has been obsolete for 15 years at least, sys/joystick.h is included in a number of graphics packages still, so that remains. A full exprun is needed before that can be removed.
RelNotes: yes Differential Revision: https://reviews.freebsd.org/D17629
show more ...
|
#
7c320a22 |
| 26-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Revert r339563.
I held the mistaken belief this was completely unused. While the driver is unused and likely not relevant for a long time, sys/joystick.h lives on in maybe half a dozen ports, even t
Revert r339563.
I held the mistaken belief this was completely unused. While the driver is unused and likely not relevant for a long time, sys/joystick.h lives on in maybe half a dozen ports, even though hardware to use it hasn't been widely used in maybe 15 years.
show more ...
|
#
c6879c6c |
| 23-Oct-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r339015 through r339669.
|
#
6a186782 |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove the ncr(4) drive.
This driver has been obsolete since the FreeBSD 4.x. It should have been removed then since the sym(4) driver had subsumed it. The driver was commented out of GENERIC in 200
Remove the ncr(4) drive.
This driver has been obsolete since the FreeBSD 4.x. It should have been removed then since the sym(4) driver had subsumed it. The driver was commented out of GENERIC in 2000.
RelNotes: Yes
show more ...
|
#
e9b5375b |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Retire dpt(4)
Marked as gone in 12 and not relevant since the early 90s. No sightings in nycbug's dmesg database.
Relnotes: yes
|
#
a1db7455 |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove bt(4) driver
The buslogic scsi driver has been tagged as gone in 12 for some time now. Remove it. The nycbug dmesg database shows only one sighting in 6 for this driver. It was very popular i
Remove bt(4) driver
The buslogic scsi driver has been tagged as gone in 12 for some time now. Remove it. The nycbug dmesg database shows only one sighting in 6 for this driver. It was very popular in the early days of the project, but that popularity seems to have died by 2004 when the nycbug database started up.
Relnotes: yes
show more ...
|
#
43b16da8 |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove adv(4) and adw(4)
Remove the advanssy drivers (both adv and adw). They were tagged as gone in 12 a while qgo. The nycbug dmesg database shows this was last seen in 6 and there were only a few
Remove adv(4) and adw(4)
Remove the advanssy drivers (both adv and adw). They were tagged as gone in 12 a while qgo. The nycbug dmesg database shows this was last seen in 6 and there were only a few adv sightings then (none for adw).
Relnotes: yes
show more ...
|
#
c24bd33d |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove aic(4) driver
aic was marked to be gone in 12 a while ago. Go ahead and remove it. nycbug's dmesg database shows this was last seen in 6 and one more time in 4.x. It never was popular, and wh
Remove aic(4) driver
aic was marked to be gone in 12 a while ago. Go ahead and remove it. nycbug's dmesg database shows this was last seen in 6 and one more time in 4.x. It never was popular, and what popularity it had was over before the nycbug databse got going in 2004.
Relnotes: yes
show more ...
|
#
39c362e0 |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove aha(4) from the tree.
We tagged aha as gone in 12 a while ago. Proceed with its removal. Data from nycbug's database shows the last sighting of this driver in 6, with the prior one in 4.x sho
Remove aha(4) from the tree.
We tagged aha as gone in 12 a while ago. Proceed with its removal. Data from nycbug's database shows the last sighting of this driver in 6, with the prior one in 4.x show its popularity had died prior to 4.x.
Relnotes: yes
show more ...
|
#
33a54d77 |
| 22-Oct-2018 |
Warner Losh <imp@FreeBSD.org> |
Remove joy(4) driver.
This driver was marked as gone in 12. We're at 13 now. Remove it. Data from nycbug's dmesg cache shows only one potential user, suggesting it never was used much.
RelNotes: ye
Remove joy(4) driver.
This driver was marked as gone in 12. We're at 13 now. Remove it. Data from nycbug's dmesg cache shows only one potential user, suggesting it never was used much.
RelNotes: yes Differential Revision: https://reviews.freebsd.org/D17629
show more ...
|
#
da2d1e9d |
| 29-Aug-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r338298 through r338391.
|
#
19fa89e9 |
| 26-Aug-2018 |
Mark Murray <markm@FreeBSD.org> |
Remove the Yarrow PRNG algorithm option in accordance with due notice given in random(4).
This includes updating of the relevant man pages, and no-longer-used harvesting parameters.
Ensure that the
Remove the Yarrow PRNG algorithm option in accordance with due notice given in random(4).
This includes updating of the relevant man pages, and no-longer-used harvesting parameters.
Ensure that the pseudo-unit-test still does something useful, now also with the "other" algorithm instead of Yarrow.
PR: 230870 Reviewed by: cem Approved by: so(delphij,gtetlow) Approved by: re(marius) Differential Revision: https://reviews.freebsd.org/D16898
show more ...
|
#
7847e041 |
| 24-Aug-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r338026 through r338297, and resolve conflicts.
|
#
4ca8c1ef |
| 23-Aug-2018 |
Conrad Meyer <cem@FreeBSD.org> |
KASSERT: Make runtime optionality optional
Add an option, KASSERT_PANIC_OPTIONAL, that allows runtime KASSERT() behavior changes. When this option is not enabled, code that allows KASSERTs to becom
KASSERT: Make runtime optionality optional
Add an option, KASSERT_PANIC_OPTIONAL, that allows runtime KASSERT() behavior changes. When this option is not enabled, code that allows KASSERTs to become optional is not enabled, and all violated assertions cause termination.
The runtime KASSERT behavior was added in r243980.
One important distinction here is that panic has __dead2 ("attribute((noreturn))"), while kassert_panic does not. Static analyzers like Coverity understand __dead2. Without it, KASSERTs go misunderstood, resulting in many false positives that result from violation of program invariants.
Reviewed by: jhb, jtl, np, vangyzen Relnotes: yes Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D16835
show more ...
|
#
14b841d4 |
| 11-Aug-2018 |
Kyle Evans <kevans@FreeBSD.org> |
MFH @ r337607, in preparation for boarding
|
#
f9c0a512 |
| 10-Aug-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r337286 through r337585.
|
#
2a4650cc |
| 09-Aug-2018 |
Kyle Evans <kevans@FreeBSD.org> |
BOOT_TAG: Make a config(5) option, expose as sysctl and loader tunable
BOOT_TAG lived shortly in sys/msgbuf.h, but this wasn't necessarily great for changing it or removing it. Move it into subr_prf
BOOT_TAG: Make a config(5) option, expose as sysctl and loader tunable
BOOT_TAG lived shortly in sys/msgbuf.h, but this wasn't necessarily great for changing it or removing it. Move it into subr_prf.c and add options for it to opt_printf.h.
One can specify both the BOOT_TAG and BOOT_TAG_SZ (really, size of the buffer that holds the BOOT_TAG). We expose it as kern.boot_tag and also add a loader tunable by the same name that we'll fetch upon initialization of the msgbuf.
This allows for flexibility and also ensures that there's a consistent way to figure out the boot tag of the running kernel, rather than relying on headers to be in-sync.
Prodded super-super-lightly by: imp
show more ...
|
#
bbd7a929 |
| 04-Aug-2018 |
Dimitry Andric <dim@FreeBSD.org> |
Merge ^/head r336870 through r337285, and resolve conflicts.
|
#
b5988450 |
| 01-Aug-2018 |
Ravi Pokala <rpokala@FreeBSD.org> |
Remove jedec_ts(4)
The jedec_ts(4) driver has been marked as deprecated in stable/11, and is now being removed from -HEAD. Add a notice in UPDATING, and update the few remaining references (regardin
Remove jedec_ts(4)
The jedec_ts(4) driver has been marked as deprecated in stable/11, and is now being removed from -HEAD. Add a notice in UPDATING, and update the few remaining references (regarding jedec_dimm(4)'s compatibility and history) to reflect the fact that jedec_ts(4) is now deleted.
Reviewed by: avg Relnotes: yes Differential Revision: https://reviews.freebsd.org/D16537
show more ...
|
#
3496c981 |
| 20-Jul-2018 |
Ian Lepore <ian@FreeBSD.org> |
Make it possible to run ntpd as a non-root user, add ntpd uid and gid.
Code analysis and runtime analysis using truss(8) indicate that the only privileged operations performed by ntpd are adjusting
Make it possible to run ntpd as a non-root user, add ntpd uid and gid.
Code analysis and runtime analysis using truss(8) indicate that the only privileged operations performed by ntpd are adjusting system time, and (re-)binding to privileged UDP port 123. These changes add a new mac(4) policy module, mac_ntpd(4), which grants just those privileges to any process running with uid 123.
This also adds a new user and group, ntpd:ntpd, (uid:gid 123:123), and makes them the owner of the /var/db/ntp directory, so that it can be used as a location where the non-privileged daemon can write files such as the driftfile, and any optional logfile or stats files.
Because there are so many ways to configure ntpd, the question of how to configure it to run without root privs can be a bit complex, so that will be addressed in a separate commit. These changes are just what's required to grant the limited subset of privs to ntpd, and the small change to ntpd to prevent it from exiting with an error if running as non-root.
Differential Revision: https://reviews.freebsd.org/D16281
show more ...
|
#
2d7e9271 |
| 12-Jul-2018 |
Ian Lepore <ian@FreeBSD.org> |
Add various spi devices to NOTES. Add some required options for building the cqspi and n25q drivers.
|
Revision tags: release/11.2.0 |
|
#
1fcf4de0 |
| 21-Jun-2018 |
Ian Lepore <ian@FreeBSD.org> |
Incorporate bus and chip select numbers into spigen(4) cdev names. Rather than assigning spigen device names in order of creation, this uses a device name that corresponds to the owning spibus and c
Incorporate bus and chip select numbers into spigen(4) cdev names. Rather than assigning spigen device names in order of creation, this uses a device name that corresponds to the owning spibus and chip-select index.
Example: /dev/spigen0.1 would be a child of spibus0, and use cs = 1
The intent is for systems like Raspberry Pi to have a consistent way of using an SPI interface with a specific cs value from a user application. Otherwise, there is no consistent way of knowing which cs pin will be assigned to a particular spigen device. The alternative is to specify everything in "the right order" in an overlay file, which is less than ideal. Additionally, this duplicates (to some extent) the way Linux handles a similar situation with their 'spidev' device, so it would be somewhat familiar to those who also use Linux.
A new kernel config option, SPIGEN_LEGACY_CDEVNAME, causes the driver to also create /dev/spigenN device name aliases, with N incrementing in the order of device instantiation. This is provided to ease the transition for existing systems using the original naming convention (particularly when these changes are MFC'd to stable branches).
Differential Revision: https://reviews.freebsd.org/D15301
show more ...
|