<?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 Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>21060372 - Merge from stable/12 r352735 and r352741</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#21060372</link>
        <description>Merge from stable/12 r352735 and r352741Merge all the stability fixes for the mpr and mps drivers. This fixes anumber of different panics. Unfortunately, mps now requires atomic_swap_64to work properly, so it has been disabled on 32-bit powerpc and mips. Theimpact should be negligible, however, since this device is difficult toattach to those platforms.Approved by:	re@ (glen)Relnotes:	YES (for ppc32 removal)

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Thu, 26 Sep 2019 16:51:51 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>2f3cabf9 - MFC r345350, r346441, r346765</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#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/modules/Makefile</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>187f36e9 - MFC r343826, r346698, r349057-r349060, r349073-r349077, r349080-r349086, r349088,</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#187f36e9</link>
        <description>MFC r343826, r346698, r349057-r349060, r349073-r349077, r349080-r349086, r349088,    r349091-r349097, r349115, r349119, r349130-r349132, r349143-r349145,    r349164-r349168, r349174, r349269-r349273r343826 by yuripv:pwm.8: fix markup in synopsis, add -f descriptionr346698 by manu:arm: allwinner: aw_pwm: compile it as module toor349057:Allow pwm(9) components to be selected individually, while &apos;device pwm&apos;still includes it all.r349058:In detach(), check for failure of bus_generic_detach(), only releaseresources if they got allocated (because detach() gets called from attach()to handle various failures), and delete the pwmbus child if it got created.r349059:Don&apos;t call pwmbus_attach_bus(), because it may not be present if thisdriver is compiled into the kernel but pwmbus will be loaded as a modulewhen needed (and because of that, pwmbus_attach_bus() is going away inthe near future).  Instead, just directly do what that function did:register the fdt xfef handle, and attach the pwmbus.r349060:Handle failure to enable the clock or obtain its frequency.r349073:Do not include pwm.h here, it is purely a userland interface file containingioctl defintions for the pwmc driver. It is not part of the pwmbus interface.r349074:Move/rename the sys/pwm.h header file to dev/pwm/pwmc.h.  The file containsioctl definitions and related datatypes that allow userland control of pwmhardware via the pwmc device.  The new name and location better reflects itsassocation with a single device driver.r349075:Remove pwmbus_attach_bus(), it no longer has any callers.  Also remove acouple prototypes for functions that never existed (and never will).r349076:Use device_delete_children() instead of a locally-rolled copy of it thatleaks the device-list memory.r349077:Add a missing #include.  I suspect this used to get included via some headerpollution that was cleaned up recently, and this file got missed in thecleanup because it&apos;s not attached to the build unless you specificallyrequest this device in a custom kernel config.r349080:Make pwmbus driver and devclass vars static; they&apos;re not mentioned in anyheader file, so they can&apos;t be used outside this file anyway.r349081:Unwrap prototype lines so that return type and function name are on thesame line.  No functional changes.r349082:Spell unsigned int as u_int and channel as chan; eliminates the need to wrapsome long lines.r349083:Give the aw_pwm driver a module version.r349084:Rename the channel_max method to channel_count, because that&apos;s what it&apos;sreturning.  (If the channel count is 2, then the max channel number is 1.)r349085:Destroy the cdev on device detach.  Also, make the driver and devclassstatic, because nothing outside this file needs them.r349086:Restructure the pwm device hirearchy and interfaces.The pwm and pwmbus interfaces were nearly identical, this merges them into asingle pwmbus interface.  The pwmbus driver now implements the pwmbusinterface by simply passing all calls through to its parent (the hardwaredriver).  The channel_count method moves from pwm to pwmbus, and theget_bus method is deleted (just no longer needed).The net effect is that the interface for doing pwm stuff is now the sameregardless of whether you&apos;re a child of pwmbus, or some random driverelsewhere in the hierarchy that is bypassing the pwmbus layer and is talkingdirectly to the hardware driver via cross-hierarchy connections establishedusing fdt data.The pwmc driver is now a child of pwmbus, instead of being its sibling(that&apos;s why the get_bus method is no longer needed; pwmc now gets thedevice_t of the bus using device_get_parent()).r349088:Make pwm channel numbers unsigned.r349091:The pwm interface was replaced with pwmbus, include the right header file.r349092:Make channel number unsigned, and spell unsigned int u_int.  This shouldhave been part of r349088.r349093:This code no longer uses fdt/ofw stuff, no need to include ofw headers.r349094:Add module makefiles for pwm.r349095:Split the dtb MODULES_EXTRA line to a series of += lines, making it easierto maintain and keep in alphabetical order, and paving the way for addingsome other modules that aren&apos;t dtb-related.r349096:Add module makefiles for Texas Instruments ARM SoCs.The natural place to look for them based on how other SoCs are organizedwould be sys/modules/ti, but that&apos;s already taken.  Drop a clue intomodules/ti/Makefile directing people to modules/arm_ti if they&apos;re lookingfor ARM modules.r349097:Build SoC-specific modules with GENERIC for the SoCs that have them.r349115:Rename pwmbus.h to ofw_pwm.h, because after all the recent changes, thereis nothing left in the file that related to pwmbus at all.  It just containsprototypes for the functions implemented in dev/pwm.ofw_pwm.c, so name itaccordingly and fix the include protect wrappers to match.A new pwmbus.h will be coming along in a future commit.r349119:Rework pwmbus and pwmc so that each child will handle a single PWM channel.Previously, there was a pwmc instance for each instance of pwm hardwareregardless of how many pwm channels that hardware supported.  Now therewill be a pwmc instance for each channel when the hardware supportsmultiple channels.  With a separate instance for each channel, we can have&quot;named channels&quot; in userland by making devfs alias entries in /dev/pwm.These changes add support for ivars to pwmbus, and use an ivar to track thechannel number for each child.  It also adds support for hinted children.In pwmc, the driver checks for a label hint, and if present, it&apos;s used tocreate an alias for the cdev in /dev/pwm.  It&apos;s not anticipated that hintswill be heavily used, but it&apos;s easy to do and allows quick ad-hoc creationof named channels from userland by using kenv to create hint.pwmc.N.label=hints.  Upcoming changes will add FDT support, and most labels willprobably be specified that way.r349130:Add ofw_pwmbus to enumerate pwmbus devices on systems configured with fdtdata.  Also, add fdt support to pwmc.r349131:Implement the ofw_bus_get_node method in aw_pwm(4) so that ofw_pwmbus canfind its metadata for instantiating children.r349132:Add back a const qualifier I somehow fumbled away between test-buildingand committing recent changes.r349143:Put the pwmc cdev filenames under the pwm directory along with any labelnames.  I.e., everything related to pwm now goes in /dev/pwm.  This willmake it easier for userland tools to turn an unqualified name into a fullyqualified pathname, whether it&apos;s the base pwmcX.Y name or a label name.r349144:Follow changes in the pwmc(4) driver in relation to device filenames.The driver now names its cdev nodes pwmcX.Y where X is unit number andY is the channel within that unit.  Change the default device name frompwmc0 to pwmc0.0.  The driver now puts cdev files and label aliases inthe /dev/pwm directory, so allow the user to provide unqualified nameswith -f and automatically prepend the /dev/pwm part for them.Update the examples in the manpage to show the new device name formatand location within /dev/pwm.r349145:Put periods at the ends of argument descriptions.  Explain the relationshipbetween the period and duty arguments.r349164:Remove everything related to channels from the pwmc public interface, nowthat there is a pwmc(4) instance per channel and the channel number ismaintained as a driver ivar rather than being passed in from userland.r349165:Explain the relationship between PWM hardware channels being controlled andpwmc(4) device filenames.  Also, use uppercase PWM when the term is beingused as an acronym, and expand the acronym where it&apos;s first used.r349166:Rearrange the argument checking and processing so that enable and disablecan be combined with configuring the period and duty cycle (the same ioctlsets all 3 values at once, so there&apos;s no reason to require the user to runthe program twice to get all 3 things set).r349167:Oops, it seems I left out the word &apos;cycle&apos;, fix it.r349168:Add a pwmc(4) manpage.r349174:Handle labels specified with hints even on FDT systems.  Hints are theeasiest thing for a user to control (via loader.conf or kenv+kldload), sohandle them in addition to any label specified via the FDT data.r349269:Some mundane tweaks and cleanups to help de-clutter the diffs of someupcoming functional changes.Add an ofw_compat_data table for probing compat strings, and use it to addPNP data.  Remove some stray semicolons at the end of macro definitions,and add a PWM_LOCK_ASSERT macro to round out the usual suite.  Move thedevice_t and driver_methods structs to the end of the file.  Tweak comments.r349270:Add support for the PWM(9) API.  This allows configuring the pwm output usingpwm(9), but also maintains the historical sysctl config interface forcompatiblity with existing apps.  The two config systems are not compatiblewith each other; if you use both interfaces to change configurations you&apos;relikely to end up with incorrect output or none at all.r349271:Catch up with recent changes in pwmbus(9).  The pwm(9) and pwmbus(9)interfaces were unified into pwmbus(9), and the PWMBUS_CHANNEL_MAX methodwas renamed PWMBUS_CHANNEL_COUNT.  The pwmbus_attach_bus() function justwent away completely.  Also, fix a few typos such as s/is/if/.r349272:Do some general cleanup and light wordsmithing.Sort methods alphabetically.  Wrap long lines.  Start sentences on a newline.  Remove contractions (not because it&apos;s a good idea, just to silenceigor).  Add some explanation of the units for the period and duty argumentsand the convention for channel numbers.r349273:Add pwm to the armv7 GENERIC kernel, it&apos;s now used by TI and Allwinner.

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Wed, 26 Jun 2019 17:28:55 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>e707f932 - MFC r346598: Enable Mellanox drivers (modules) on AArch64</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#e707f932</link>
        <description>MFC r346598: Enable Mellanox drivers (modules) on AArch64PR:		237055Submitted by:	Greg V &lt;greg@unrelenting.technology&gt;

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Fri, 24 May 2019 13:39:56 +0000</pubDate>
        <dc:creator>Ed Maste &lt;emaste@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/modules/Makefile#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/modules/Makefile</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>c0826cde - MFC r345407,r345408: Add nvme to arm64 GENERIC, and build if_ena on arm64.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#c0826cde</link>
        <description>MFC r345407,r345408: Add nvme to arm64 GENERIC, and build if_ena on arm64.These allow stable/12 to boot on Amazon EC2 &quot;A1&quot; family (arm64) instances.Sponsored by:	https://www.patreon.com/cperciva

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Sat, 27 Apr 2019 19:48:15 +0000</pubDate>
        <dc:creator>Colin Percival &lt;cperciva@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b90d8d4f - MFC r344505-r344507, r344523, r344525-r344526, r344529, r344606-r344612,</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#b90d8d4f</link>
        <description>MFC r344505-r344507, r344523, r344525-r344526, r344529, r344606-r344612,r344614-r344616, r344681, r344684-r344686, r344728, r344733-r344734, r344981A large set of changes that collectively modernize the at45d and mx25l(DataFlash and SpiFlash) drivers, add FDT support, and add geom_flashmap andgeom_label support to them.r344505:Add a functional detach() implementation to make module unloading possible.r344506:Add support for probing/attaching on FDT-based systems.r344507:Switch to using config_intrhook_oneshot().  That allows the error handlingin the delayed attach to use early returns, which allows reducing the levelof indentation.  So all in all, what looks like a lot of changes is reallyno change in behavior, mostly just moving whitespace around.r344523:Include the jedec &quot;extended device information string&quot; in the criteria usedto match a chip to our table of metadata describing the chips. At least onenew DataFlash chip has a 3-byte jedec ID identical to its predecessors anddiffers only in the extended info, and it has different metadata requiring aunique entry in the table.  This paves the way for supporting such chips.The metadata table now includes two new fields, extmask and extid.  The twobytes of extended info obtained from the chip are ANDed with extmask thencompared to extid, so it&apos;s possible to use only a subset of the extendedinfo in the matching.We now always read 6 bytes of jedec ID info. Most chips don&apos;t return anyextended info, and the values read back for those two bytes may beindeterminate, but such chips have extmask and extid values of 0x0000 in thetable, so the extid effectively doesn&apos;t participate in the matching on thosechips and it doesn&apos;t matter what they return in the extended info bytes.r344525:Add a metadata entry for the AT45DB641E chip.  This chip has the same 3-bytejedec ID as its older cousin the AT45DB642D, but uses a different page size.The only way to distinguish between the two chips is that the 2D chip has0 bytes of extended ID info and the new 1E has 1 byte of extended ID.  Theactual value of the extended ID byte is all zeroes.  In other words, it&apos;sthe presence of the extended info that identifies this chip. (Presumablya future upgrade might define non-zero values for the extended ID byte.)r344526:Resolve a name conflict when both SpiFlash and DataFlash devices are present.Both SpiFlash (mx25l) and DataFlash (at45d) drivers create a disk devicewith a name of /dev/flash/spiN where N is the driver&apos;s unit number.  Ifboth types of devices are present in the same system, this creates a fatalconflict that prevents attachment of whichever device attaches second(because mx25l0 and at45d0 both try to create a spi0).This gives each type of device a unique name (mx25lN or at45dN respectively)and also adds an alias of spiN for compatibility.  When both device typesappear in the same system, only the first to attach gets the spiN alias.When the second device attaches there is a non-fatal warning that the aliascan&apos;t be created, but both devices are still accessible via their primarynames (and there is no need for the spiN name to work for backwardscompatibility on such a system, because it has never been possible to usethe spiN names when both devices exist).r344529:Fix a paste-o that broke the build on all arches.r344606:Add support for geom_flashmap by providing a getattr() for &quot;SPI:device&quot;.r344607:Compile fdt_slicer and geom_flashmap when the at45d device is included.r344608:Update a comment to reflect reality; no functional changes.r344609:Make it possible to load fdt_slicer as a module (unloading works too fwiw).r344610:Add manpages for at45d(4) and mx25l(4).r344611:Add a module dependency on fdt_slicer.r344612:Add a module dependency on fdt_slicer.  Also, move the PNP_INFO to its moreusual location, down near the DRIVER_MODULE() stuff.r344614:Rename some functions and variables to have shorter names, which allowsunwrapping multiple lines of code.  Also, convert some short multilinecomments into single-line comments.  Change old-school FALSE to false.All in all, no functional changes, it&apos;s just more compact and readable.r344615:Child nodes with a compatible property are not slices, according to thedevicetree/bindings/mtd/partitions.txt document, so just ignore them.r344616:Add support to fdt_slicer for the new style partition data documented indevicetree/bindings/mtd/partition.txt.In the old style, all the children of the device node which did not have acompatible property were the partitions.  In the new style, there is a childnode of the device which has a compatible string of &quot;fixed-partitions&quot;, andits children are the individual partitions.Also, support the read-only property by setting the corresponding slice flag.r344681:Build fdt support modules on systems that use fdt data.kern.opts.mk sets make var OPT_FDT to a non-empty value if platform.hcontains OPT_FDT.r344684:Undo accidental part of r344681.I think I must have accidentally mouse-click pasted while scrolling anddidn&apos;t notice it.Reported by:	jhibbits@r344685:Add required header file to SRCS.r344686:Add another required header file.For some reason this seems to be required on aarch64, but I can build armv7from clean without needing this in the list.  (The file does get included,so the mystery is why armv7 works.)r344728:Bugfix: use a dummy buffer for the inactive side of a transfer.This is especially important for writes.  SPI is inherently a bidirectionalbus; you receive data (even if it&apos;s garbage) while writing.  We should notreceive that data into the same buffer we&apos;re writing to the device.When reading it doesn&apos;t matter what we send to the device, but using thedummy buffer for that as well is pleasingly symmetrical.r344733:Add some comments.  Give #define&apos;d names to some scattered numbers.  Changesome #define&apos;d names to be more descriptive.  When reporting a post-writecompare failure, report the page number, not the byte address of the page.The latter is the only functional change, it makes the number match thewords of the error message.r344734:Allow the sector size of the disk device to be configured using hints orFDT data.  The sector size must be a multiple of the device&apos;s page size.If not configured, use the historical default of the device page size.Setting the disk sector size to 512 or 4096 allows a variety of standardfilesystems to be used on the device.  Of course you wouldn&apos;t want to bewriting frequently to a SPI flash chip like it was a disk drive, but fordata that gets written once (or rarely) and read often, using a standardfilesystem is a nice convenient thing.r344981:Give the mx25l device sole ownership of the name /dev/flash/spi* instead oftrying to use disk_add_alias() to make spi* an alias for mx25l*.  It turnsout disk_add_alias() works for partitions, but not slices, and that&apos;s hardto fix.This change is, in effect, a partial revert of r344526.The mips world relies on the existence of flashmap names formatted as/dev/flash/spi0s.name, whereas pretty much nothing relies on at45d devicesusing the /dev/spi* names (because until recently the at45d driver didn&apos;teven work reliably). So this change makes mx25l devices the sole owner ofthe /dev/flash/spi* namespace, which actually makes some sense because it isa SpiFlash(tm) device, so flash/spi isn&apos;t a horrible name.

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Mon, 22 Apr 2019 00:38:25 +0000</pubDate>
        <dc:creator>Ian Lepore &lt;ian@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/modules/Makefile#b57c318b</link>
        <description>MFC r344479 (by sobomax), r344605:Modularize xz.

            List of files:
            /freebsd-12.1/sys/modules/Makefile</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>0eecda31 - MFC r343617, r343618:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#0eecda31</link>
        <description>MFC r343617, r343618:Make iflib a loadable module.

            List of files:
            /freebsd-12.1/sys/modules/Makefile</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>0379d92f - MFC r339523:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#0379d92f</link>
        <description>MFC r339523:Add amdgpio, driver for GPIO controller on AMD-based x86_64 platformsSubmitted by:	Rajesh Kumar &lt;rajbsd@gmail.com&gt;Differential Revision:	https://reviews.freebsd.org/D16865

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Mon, 26 Nov 2018 22:00:29 +0000</pubDate>
        <dc:creator>Oleksandr Tymoshenko &lt;gonzo@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>6db7f8e5 - Add initial driver for ACPI NFIT-enumerated NVDIMMs.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#6db7f8e5</link>
        <description>Add initial driver for ACPI NFIT-enumerated NVDIMMs.Driver enumerates NVDIMMs.  Besides, for each found System PhysicalAddress (SPA) range, spaN geom provider is created, which allowsformatting and mounting the region as the normal volume.  Also,/dev/nvdimm_spaN node is created, which can be read/written/mapped byuserspace, the mapping is zero-copy.No support for block access methods implemented, labels are notparsed.   No management interfaces are provided.Tested by:	Intel, NetAppSponsored by:	The FreeBSD FoundationApproved by:	re (gjb)MFC after:	2 weeks

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Tue, 16 Oct 2018 20:12:35 +0000</pubDate>
        <dc:creator>Konstantin Belousov &lt;kib@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>77c1fcec - ixl/iavf(4): Change ixlv to iavf and update it to use iflib(9)</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#77c1fcec</link>
        <description>ixl/iavf(4): Change ixlv to iavf and update it to use iflib(9)Finishes the conversion of the 40Gb Intel Ethernet drivers to iflib(9) forFreeBSD 12.0, and fixes numerous bugs in both ixl(4) and iavf(4).This commit also re-adds the VF driver to GENERIC since it now compiles andfunctions.The VF driver name was changed from ixlv(4) to iavf(4) because the VF driver isnow intended to be used with future products, not just with Fortville/Fort ParkVFs.A man page update that documents these drivers is forthcoming in a separatecommit.Reviewed by:    sbruno@, kbowling@Tested by:      jeffrey.e.pieper@intel.comApproved by:	re (gjb@)Relnotes:       yesSponsored by:   Intel CorporationDifferential Revision: https://reviews.freebsd.org/D16429

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Fri, 12 Oct 2018 22:40:54 +0000</pubDate>
        <dc:creator>Eric Joyner &lt;erj@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>c0386fa3 - Put building of drm and drm2 modules behind options.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#c0386fa3</link>
        <description>Put building of drm and drm2 modules behind options.Make the building of drm dependent on MK_MODULE_DRM and the buildingof module drm2 on MK_MODULE_DRM2. The defaults are unchanged.Approved by: re@ (gjb)Differential Review: https://reviews.freebsd.org/D16894

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Tue, 28 Aug 2018 14:46:49 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@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/modules/Makefile#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/modules/Makefile</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>592ffb21 - Revert drm2 removal.</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#592ffb21</link>
        <description>Revert drm2 removal.Revert r338177, r338176, r338175, r338174, r338172After long consultations with re@, core members and mmacy, revertthese changes. Followup changes will be made to mark them asdeprecated and prent a message about where to find the up-to-datedriver.  Followup commits will be made to make this clear in theinstaller. Followup commits to reduce POLA in ways we&apos;re stillexploring.It&apos;s anticipated that after the freeze, this will be removed in13-current (with the residual of the drm2 code copied tosys/arm/dev/drm2 for the TEGRA port&apos;s use w/o the intel orradeon drivers).Due to the impending freeze, there was no formal core vote forthis. I&apos;ve been talking to different core members all day, as well asMatt Macey and Glen Barber. Nobody is completely happy, all aregrudgingly going along with this. Work is in progress to mitigatethe negative effects as much as possible.Requested by: re@ (gjb, rgrimes)

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Fri, 24 Aug 2018 00:02:00 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>d157fbd5 - Remove legacy drm and drm2 from tree</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#d157fbd5</link>
        <description>Remove legacy drm and drm2 from treeAs discussed on the MLs drm2 conflicts with the ports&apos; version and thereis no upstream for most if not all of drm. Both have been merged in toa single port.Users on powerpc, 32-bit hardware, or with GPUs predating Radeonand i915 will need to install the graphics/drm-legacy-kmod. Allother users should be able to use one of the LinuxKPI-based ports:graphics/drm-stable-kmod, graphics/drm-next-kmod, graphics/drm-devel-kmod.MFC: neverApproved by: core@

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Wed, 22 Aug 2018 01:50:12 +0000</pubDate>
        <dc:creator>Matt Macy &lt;mmacy@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>0bf0bb83 - Support building IPMI as a module on powerpc64</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#0bf0bb83</link>
        <description>Support building IPMI as a module on powerpc64This still only supports IPMI via OPAL on powerpc64, but now it can be testedwith a GENERIC kernel.

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Wed, 25 Jul 2018 18:58:57 +0000</pubDate>
        <dc:creator>Justin Hibbits &lt;jhibbits@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/modules/Makefile#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/modules/Makefile</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>e18e6384 - Partial revert of r335399 and r335400:</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#e18e6384</link>
        <description>Partial revert of r335399 and r335400:Unhook the MAC/veriexec, fingerprint handlers, and veriexec modules fromthe kernel modules Makefile.Reviewed by:	sjg

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Tue, 26 Jun 2018 23:28:03 +0000</pubDate>
        <dc:creator>Stephen J. Kiernan &lt;stevek@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>408ab1bd - Correct linprocfs/linsysfs arch check in r335672</title>
        <link>http://172.16.0.5:8080/history/freebsd-12.1/sys/modules/Makefile#408ab1bd</link>
        <description>Correct linprocfs/linsysfs arch check in r335672Pointy hat to:	emaste

            List of files:
            /freebsd-12.1/sys/modules/Makefile</description>
        <pubDate>Tue, 26 Jun 2018 19:13:49 +0000</pubDate>
        <dc:creator>Ed Maste &lt;emaste@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
