<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in NOTES</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>2f3cabf9 - MFC r345350, r346441, r346765</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#2f3cabf9</link>
        <description>MFC r345350, r346441, r346765r345350:Rename fuse(4) to fusefs(4)This makes it more consistent with other filesystems, which all end in &quot;fs&quot;,and more consistent with its mount helper, which is already named&quot;mount_fusefs&quot;.Reviewed by:	cem, rgrimesSponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D19649r346441:Use symlinks for kernel modules rather than hardlinksWhen aliasing a kernel module to a different name (ie if_igb for if_em),it&apos;s better to use symlinks than hard links. kldxref will omit entries forthe links, ensuring that the loaded module has the correct name.Reviewed by:	impSponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D19979r346765:Don&apos;t symlink fusefs.ko to fuse.ko on PPCSome PPC systems (PowerNV) use msdosfs for /boot, which can&apos;t handle eithersymlinks or hardlinks. So on PPC, copy the module instead. This change fixesinstallkernel on such systems after r345350.Reported by:	Brandon Bergren &lt;git_bdragon.rtk0.net&gt;Reviewed by:	jhibbits, rgrimesMFC-With:	345350, 346441Sponsored by:	The FreeBSD FoundationDifferential Revision:	https://reviews.freebsd.org/D19993

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Fri, 06 Sep 2019 17:21:21 +0000</pubDate>
        <dc:creator>Alan Somers &lt;asomers@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>e27633af - MFC r350591, r350971, r351724</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#e27633af</link>
        <description>MFC r350591, r350971, r351724r350591:Add a driver for Texas Instruments ADS101x/ADS111x i2c ADC chips.Instances of the device can be configured using hints or FDT data.Interfaces to reconfigure the chip and extract voltage measurements fromit are available via sysctl(8).r350971:Fix the driver name in ads111x.4, and hook the manpage up to the build.The driver was originally written with the name ads1115, but at the lastminute it got renamed to ads111x to reflect its support for many relatedchips, but I forgot to update the manpage to match the renaming beforecommitting it all.r351724:Fix the name of the devicetree bindings document file cited in the manpage.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 05 Sep 2019 16:37:10 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>8f318f29 - MFC r349319, r349328-r349330</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#8f318f29</link>
        <description>MFC r349319, r349328-r349330r349319:Add some i2c slave-device drivers that were missing from NOTES.r349328:The gpiopps(4) driver currently has probe and attach code only for FDT basedsystems, so conditionalize it accordingly in conf/files.r349329:Add gpio(4) and related drivers to NOTES.r349330:Add pwm devices to NOTES.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Sun, 11 Aug 2019 21:15:30 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>c1dbe4cb - MFC r347285 and r347327:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#c1dbe4cb</link>
        <description>MFC r347285 and r347327:Initial version of Mellanox in-kernel firmware upgrade support.Submitted by:	slavash@Sponsored by:	Mellanox Technologies

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 16 May 2019 16:09:16 +0000</pubDate>
        <dc:creator>Hans Petter Selasky &lt;hselasky@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>3c239409 - MFC r346544:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#3c239409</link>
        <description>MFC r346544:Clarify the relationship between INVARIANTS and DIAGNOSTIC a bit.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Mon, 29 Apr 2019 13:20:24 +0000</pubDate>
        <dc:creator>Mark Johnston &lt;markj@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>165d2144 - MFC r345680: NOTES: Use non-default value for BOOT_TAG</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#165d2144</link>
        <description>MFC r345680: NOTES: Use non-default value for BOOT_TAG

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Mon, 08 Apr 2019 18:36:47 +0000</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b57c318b - MFC r344479 (by sobomax), r344605:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#b57c318b</link>
        <description>MFC r344479 (by sobomax), r344605:Modularize xz.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Tue, 19 Mar 2019 17:16:37 +0000</pubDate>
        <dc:creator>Konstantin Belousov &lt;kib@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>30985a03 - MFC r344702: There is no `device atacard` but there is `device atapccard`.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#30985a03</link>
        <description>MFC r344702: There is no `device atacard` but there is `device atapccard`.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Fri, 08 Mar 2019 00:53:11 +0000</pubDate>
        <dc:creator>Alexander Motin &lt;mav@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>015c5ac3 - MFC r344198:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#015c5ac3</link>
        <description>MFC r344198:GC ATA_REQUEST_TIMEOUT option remnantsIt was removed from code in r249083 and from sys/conf/options in r249213.PR:		193935, 222170

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 21 Feb 2019 09:54:10 +0000</pubDate>
        <dc:creator>Andriy Voskoboinyk &lt;avos@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>0eecda31 - MFC r343617, r343618:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#0eecda31</link>
        <description>MFC r343617, r343618:Make iflib a loadable module.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Fri, 15 Feb 2019 09:49:09 +0000</pubDate>
        <dc:creator>Konstantin Belousov &lt;kib@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>19fa89e9 - Remove the Yarrow PRNG algorithm option in accordance with due notice</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#19fa89e9</link>
        <description>Remove the Yarrow PRNG algorithm option in accordance with due noticegiven in random(4).This includes updating of the relevant man pages, and no-longer-usedharvesting parameters.Ensure that the pseudo-unit-test still does something useful, now alsowith the &quot;other&quot; algorithm instead of Yarrow.PR:		230870Reviewed by:	cemApproved by:	so(delphij,gtetlow)Approved by:	re(marius)Differential Revision:	https://reviews.freebsd.org/D16898

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Sun, 26 Aug 2018 12:51:46 +0000</pubDate>
        <dc:creator>Mark Murray &lt;markm@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>4ca8c1ef - KASSERT: Make runtime optionality optional</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#4ca8c1ef</link>
        <description>KASSERT: Make runtime optionality optionalAdd an option, KASSERT_PANIC_OPTIONAL, that allows runtime KASSERT()behavior changes.  When this option is not enabled, code that allowsKASSERTs to become optional is not enabled, and all violated assertionscause termination.The runtime KASSERT behavior was added in r243980.One important distinction here is that panic has __dead2(&quot;attribute((noreturn))&quot;), while kassert_panic does not.  Static analyzerslike Coverity understand __dead2.  Without it, KASSERTs go misunderstood,resulting in many false positives that result from violation of programinvariants.Reviewed by:	jhb, jtl, np, vangyzenRelnotes:	yesSponsored by:	Dell EMC IsilonDifferential Revision:	https://reviews.freebsd.org/D16835

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Wed, 22 Aug 2018 22:19:42 +0000</pubDate>
        <dc:creator>Conrad Meyer &lt;cem@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2a4650cc - BOOT_TAG: Make a config(5) option, expose as sysctl and loader tunable</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#2a4650cc</link>
        <description>BOOT_TAG: Make a config(5) option, expose as sysctl and loader tunableBOOT_TAG lived shortly in sys/msgbuf.h, but this wasn&apos;t necessarily greatfor changing it or removing it. Move it into subr_prf.c and add options forit to opt_printf.h.One can specify both the BOOT_TAG and BOOT_TAG_SZ (really, size of thebuffer that holds the BOOT_TAG). We expose it as kern.boot_tag and also adda loader tunable by the same name that we&apos;ll fetch upon initialization ofthe msgbuf.This allows for flexibility and also ensures that there&apos;s a consistent wayto figure out the boot tag of the running kernel, rather than relying onheaders to be in-sync.Prodded super-super-lightly by:	imp

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 09 Aug 2018 17:47:47 +0000</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b5988450 - Remove jedec_ts(4)</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#b5988450</link>
        <description>Remove jedec_ts(4)The jedec_ts(4) driver has been marked as deprecated in stable/11, and isnow being removed from -HEAD. Add a notice in UPDATING, and update the fewremaining references (regarding jedec_dimm(4)&apos;s compatibility and history)to reflect the fact that jedec_ts(4) is now deleted.Reviewed by:	avgRelnotes:	yesDifferential Revision:	https://reviews.freebsd.org/D16537

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Wed, 01 Aug 2018 08:24:34 +0000</pubDate>
        <dc:creator>Ravi Pokala &lt;rpokala@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>3496c981 - Make it possible to run ntpd as a non-root user, add ntpd uid and gid.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#3496c981</link>
        <description>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 onlyprivileged 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 anyprocess running with uid 123.This also adds a new user and group, ntpd:ntpd, (uid:gid 123:123), and makesthem the owner of the /var/db/ntp directory, so that it can be used as alocation where the non-privileged daemon can write files such as thedriftfile, and any optional logfile or stats files.Because there are so many ways to configure ntpd, the question of how toconfigure it to run without root privs can be a bit complex, so that will beaddressed in a separate commit. These changes are just what&apos;s required togrant the limited subset of privs to ntpd, and the small change to ntpd toprevent it from exiting with an error if running as non-root.Differential Revision:	https://reviews.freebsd.org/D16281

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 19 Jul 2018 23:55:29 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2d7e9271 - Add various spi devices to NOTES.  Add some required options for building</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#2d7e9271</link>
        <description>Add various spi devices to NOTES.  Add some required options for buildingthe cqspi and n25q drivers.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Wed, 11 Jul 2018 22:23:50 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>1fcf4de0 - Incorporate bus and chip select numbers into spigen(4) cdev names.  Rather</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#1fcf4de0</link>
        <description>Incorporate bus and chip select numbers into spigen(4) cdev names.  Ratherthan assigning spigen device names in order of creation, this uses a devicename that corresponds to the owning spibus and chip-select index.Example: /dev/spigen0.1 would be a child of spibus0, and use cs = 1The intent is for systems like Raspberry Pi to have a consistent way ofusing an SPI interface with a specific cs value from a user application.Otherwise, there is no consistent way of knowing which cs pin will beassigned to a particular spigen device. The alternative is to specifyeverything in &quot;the right order&quot; in an overlay file, which is less thanideal. Additionally, this duplicates (to some extent) the way Linux handlesa similar situation with their &apos;spidev&apos; device, so it would be somewhatfamiliar to those who also use Linux.A new kernel config option, SPIGEN_LEGACY_CDEVNAME, causes the driver toalso create /dev/spigenN device name aliases, with N incrementing in theorder of device instantiation.  This is provided to ease the transitionfor existing systems using the original naming convention (particularlywhen these changes are MFC&apos;d to stable branches).Differential Revision:	https://reviews.freebsd.org/D15301

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 21 Jun 2018 21:16:26 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>199b9ab8 - Add a note about using option VERBOSE_SYSINIT=0 to get the verbose code</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#199b9ab8</link>
        <description>Add a note about using option VERBOSE_SYSINIT=0 to get the verbose codecompiled in but disabled by default.

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 21 Jun 2018 14:59:23 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>46033610 - unbreak LINT build after r334804</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#46033610</link>
        <description>unbreak LINT build after r334804

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Fri, 08 Jun 2018 05:48:36 +0000</pubDate>
        <dc:creator>Matt Macy &lt;mmacy@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>7b2c7b92 - md: use prestaged mfs_root</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/conf/NOTES#7b2c7b92</link>
        <description>md: use prestaged mfs_rootOn PowerNV systems, the rootfs is passed through kexec, which loads the rootfsinto memory and set two fdt entries to describe where the file is located inthe memory;I need to pass this memory region to the md device as a mfs_root, but, currentmd driver does not support two things: * Just getting a pointer from an external (bootloader) memory. If I need toworkaround it, I would need to declare a static array and memcopy from thisexternal memory to this static variable. * The size of the image. The usage of mfs_root_end, which is not a pointer,seems to be not possible for this prestaged scenario.This patch simply adds a new way to load mfs_root from memory.Differential Revision: https://reviews.freebsd.org/D15625Approved by: kib, jhibbits (mentor)

            List of files:
            /freebsd-12.1/sys/conf/NOTES</description>
        <pubDate>Thu, 07 Jun 2018 13:57:34 +0000</pubDate>
        <dc:creator>Breno Leitao &lt;leitao@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
