Changes in Makefile

187f36e9 - MFC r343826, r346698, r349057-r349060, r349073-r349077, r349080-r349086, r349088,

Wed, 26 Jun 2019 17:28:55 +0000

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 'device pwm'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'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'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're not mentioned in anyheader file, so they can'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's what it'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'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'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'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's already taken. Drop a clue intomodules/ti/Makefile directing people to modules/arm_ti if they'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"named channels" 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's used tocreate an alias for the cdev in /dev/pwm. It's not anticipated that hintswill be heavily used, but it'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'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'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'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 'cycle', 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'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'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's now used by TI and Allwinner. List of files: /freebsd-12.1/include/Makefile

ae8c08e7 - Add support for loader veriexec

Fri, 12 Apr 2019 01:03:00 +0000

Add support for loader veriexecAlso sbin/veriexec for mac_veriexecMFC r343281,344564-344568,344780,344784,345289,346070 List of files: /freebsd-12.1/include/Makefile

a52fd948 - Handle -DNO_ROOT for `make compat` in include/

Thu, 23 Aug 2018 18:18:52 +0000

Handle -DNO_ROOT for `make compat` in include/Otherwise this step will fail on a Linux host due to missing "wheel" groupApproved By: brooks (mentor)Differential Revision: https://reviews.freebsd.org/D16841 List of files: /freebsd-12.1/include/Makefile

cd87846e - Install symlink for sys/nvpair.h in include/Makefile symlinks target

Mon, 13 Aug 2018 05:16:27 +0000

Install symlink for sys/nvpair.h in include/Makefile symlinks targetNoticed while fixing the install/sysroot situation for libnvpair andlibzfs_core- if one uses the symlinks target, libzfs_core.h is notinstalled. List of files: /freebsd-12.1/include/Makefile

ce33c57d - Use INCS for non-sys/ libnvpair and libzfs_core includes

Mon, 13 Aug 2018 03:38:32 +0000

Use INCS for non-sys/ libnvpair and libzfs_core includesWhile nothing was wrong with libnvpair.h, libzfs_core.h was only guarded byMK_CDDL rather than MK_CDDL && MK_ZFS. Rather than ugl'if'yinginclude/Makefile to impose the extra restriction, just move the non-sys/includes into INCS with the respect lib builds.This has the added bonus of allowing third party packagers to try and splitthese libs out of the FreeBSD-runtime package, if they are so inclined.The sys/ include was left alone- generally userland libraries shouldn'tinstall kernel headers.MFC after: 1 week List of files: /freebsd-12.1/include/Makefile

e5054602 - Import the netdump client code.

Sun, 06 May 2018 00:38:29 +0000

Import the netdump client code.This is a component of a system which lets the kernel dump core toa remote host after a panic, rather than to a local storage device.The server component is available in the ports tree. netdump isparticularly useful on diskless systems.The netdump(4) man page contains some details describing the protocol.Support for configuring netdump will be added to dumpon(8) in a futurecommit. To use netdump, the kernel must have been compiled with theNETDUMP option.The initial revision of netdump was written by Darrell Anderson andwas integrated into Sandvine's OS, from which this version was derived.Reviewed by: bdrewery, cem (earlier versions), julian, sbrunoMFC after: 1 monthX-MFC note: use a spare field in struct ifnetSponsored by: Dell EMC IsilonDifferential Revision: https://reviews.freebsd.org/D15253 List of files: /freebsd-12.1/include/Makefile

e6a376d1 - Retire lmc(4)

Tue, 01 May 2018 16:30:48 +0000

Retire lmc(4)This driver supports legacy, 32-bit PCI devices, and had an ambiguouslicense. Supported devices were already reported to be rare in 2003(when an earlier version of the driver was removed in r123201).Reviewed by: rgrimesRelnotes: YesSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D15245 List of files: /freebsd-12.1/include/Makefile

2529f56e - Add the "TCP Blackbox Recorder" which we discussed at the developer

Thu, 22 Mar 2018 09:40:08 +0000

Add the "TCP Blackbox Recorder" which we discussed at the developersummits at BSDCan and BSDCam in 2017.The TCP Blackbox Recorder allows you to capture events on a TCP connectionin a ring buffer. It stores metadata with the event. It optionally storesthe TCP header associated with an event (if the event is associated with apacket) and also optionally stores information on the sockets.It supports setting a log ID on a TCP connection and using this to correlatemultiple connections that share a common log ID.You can log connections in different modes. If you are doing a coordinatedtest with a particular connection, you may tell the system to put it inmode 4 (continuous dump). Or, if you just want to monitor for errors, youcan put it in mode 1 (ring buffer) and dump all the ring buffers associatedwith the connection ID when we receive an error signal for that connectionID. You can set a default mode that will be applied to a particular ratioof incoming connections. You can also manually set a mode using a socketoption.This commit includes only basic probes. rrs@ has added quite an abundanceof probes in his TCP development work. He plans to commit those soon.There are user-space programs which we plan to commit as ports. These readthe data from the log device and output pcapng files, and then let youanalyze the data (and metadata) in the pcapng files.Reviewed by: gnn (previous version)Obtained from: Netflix, Inc.Relnotes: yesDifferential Revision: https://reviews.freebsd.org/D11085 List of files: /freebsd-12.1/include/Makefile

e808190a - Add kernel and userspace code to dump the firmware state of supported

Thu, 08 Mar 2018 15:21:56 +0000

Add kernel and userspace code to dump the firmware state of supportedConnectX-4/5 devices in mlx5core.The dump is obtained by reading a predefined register map from thenon-destructive crspace, accessible by the vendor-specific PCIecapability (VSC). The dump is stored in preallocated kernel memory andmanaged by the mlx5tool(8), which communicates with the driver using acharacter device node.The utility allows to store the dump in format

into a file, to reset the dump content, and to manually initiate thedump.A call to mlx5_fwdump() should be added at the places where a dumpmust be fetched automatically. The most likely place is right before afirmware reset request.Submitted by: kib@MFC after: 1 weekSponsored by: Mellanox Technologies List of files: /freebsd-12.1/include/Makefile

a94a63f0 - An MMC/SD/SDIO stack using CAM

Sun, 09 Jul 2017 16:57:24 +0000

An MMC/SD/SDIO stack using CAMImplement the MMC/SD/SDIO protocol within a CAM framework. CAM'sflexible queueing will make it easier to write non-storage driversthan the legacy stack. SDIO drivers from both the kernel and asuserland daemons are possible, though much of that functionality willcome later.Some of the CAM integration isn't complete (there are sleeps in thedevice probe state machine, for example), but those minor issues canbe improved in-tree more easily than out of tree and shouldn't gateprogress on other fronts. Appologies to reviews if specific itemshave been overlooked.Submitted by: Ilya BakulinReviewed by: emaste, imp, mav, adrian, ianDifferential Review: https://reviews.freebsd.org/D4761merge with first commit, various compile hacks. List of files: /freebsd-12.1/include/Makefile

c99b67a7 - Utilize SYSROOT from r320119 in places where DESTDIR may be wanting WORLDTMP.

Mon, 19 Jun 2017 20:47:24 +0000

Utilize SYSROOT from r320119 in places where DESTDIR may be wanting WORLDTMP.Since buildenv exports SYSROOT all of these uses will now look inWORLDTMP by default.sys/boot/efi/loader/Makefile A LIBSTAND hack is no longer required for buildenv.MFC after: 2 weeksSponsored by: Dell EMC Isilon List of files: /freebsd-12.1/include/Makefile

a7dc3128 - Remove the NATM framework including the en(4), fatm(4), hatm(4), and

Mon, 24 Apr 2017 21:21:49 +0000

Remove the NATM framework including the en(4), fatm(4), hatm(4), andpatm(4) devices.Maintaining an address family and framework has real costs when we makeinfrastructure improvements. In the case of NATM we support no devicesmanufactured in the last 20 years and some will not even work in modernmotherboards (some newer devices that patm(4) could be updated tosupport apparently exist, but we do not currently have support).With this change, support remains for some netgraph modules that don'trequire NATM support code. It is unclear if all these should remain,though ng_atmllc certainly stands alone.Note well: FreeBSD 11 supports NATM and will continue to do so until atleast September 30, 2021. Improvements to the code in FreeBSD 11 arecertainly welcome.Reviewed by: philipApproved by: harti List of files: /freebsd-12.1/include/Makefile

72dec079 - - Add support for eMMC "partitions". Besides the user data area, i. e.

Thu, 16 Mar 2017 22:23:04 +0000

- Add support for eMMC "partitions". Besides the user data area, i. e. the default partition, eMMC v4.41 and later devices can additionally provide up to: 1 enhanced user data area partition 2 boot partitions 1 RPMB (Replay Protected Memory Block) partition 4 general purpose partitions (optionally with a enhanced or extended attribute) Of these "partitions", only the enhanced user data area one actually slices the user data area partition and, thus, gets handled with the help of geom_flashmap(4). The other types of partitions have address space independent from the default partition and need to be switched to via CMD6 (SWITCH), i. e. constitute a set of additional "disks". The second kind of these "partitions" doesn't fit that well into the design of mmc(4) and mmcsd(4). I've decided to let mmcsd(4) hook all of these "partitions" up as disk(9)'s (except for the RPMB partition as it didn't seem to make much sense to be able to put a file-system there and may require authentication; therefore, RPMB partitions are solely accessible via the newly added IOCTL interface currently; see also below). This approach for one resulted in cleaner code. Second, it retains the notion of mmcsd(4) children corresponding to a single physical device each. With the addition of some layering violations, it also would have been possible for mmc(4) to add separate mmcsd(4) instances with one disk each for all of these "partitions", however. Still, both mmc(4) and mmcsd(4) share some common code now e. g. for issuing CMD6, which has been factored out into mmc_subr.c. Besides simply subdividing eMMC devices, some Intel NUCs having UEFI code in the boot partitions etc., another use case for the partition support is the activation of pseudo-SLC mode, which manufacturers of eMMC chips typically associate with the enhanced user data area and/ or the enhanced attribute of general purpose partitions. CAVEAT EMPTOR: Partitioning eMMC devices is a one-time operation.- Now that properly issuing CMD6 is crucial (so data isn't written to the wrong partition for example), make a step into the direction of correctly handling the timeout for these commands in the MMC layer. Also, do a SEND_STATUS when CMD6 is invoked with an R1B response as recommended by relevant specifications. However, quite some work is left to be done in this regard; all other R1B-type commands done by the MMC layer also should be followed by a SEND_STATUS (CMD13), the erase timeout calculations/handling as documented in specifications are entirely ignored so far, the MMC layer doesn't provide timeouts applicable up to the bridge drivers and at least sdhci(4) currently is hardcoding 1 s as timeout for all command types unconditionally. Let alone already available return codes often not being checked in the MMC layer ...- Add an IOCTL interface to mmcsd(4); this is sufficiently compatible with Linux so that the GNU mmc-utils can be ported to and used with FreeBSD (note that due to the remaining deficiencies outlined above SANITIZE operations issued by/with `mmc` currently most likely will fail). These latter will be added to ports as sysutils/mmc-utils in a bit. Among others, the `mmc` tool of the GNU mmc-utils allows for partitioning eMMC devices (tested working).- For devices following the eMMC specification v4.41 or later, year 0 is 2013 rather than 1997; so correct this for assembling the device ID string properly.- Let mmcsd.ko depend on mmc.ko. Additionally, bump MMC_VERSION as at least for some of the above a matching pair is required.- In the ACPI front-end of sdhci(4) describe the Intel eMMC and SDXC controllers as such in order to match the PCI one. Additionally, in the entry for the 80860F14 SDXC controller remove the eMMC-only SDHCI_QUIRK_INTEL_POWER_UP_RESET.OKed by: impSubmitted by: ian (mmc_switch_status() implementation) List of files: /freebsd-12.1/include/Makefile

28d60d6a - Convert include over to SRCTOP

Sun, 12 Mar 2017 18:59:00 +0000

Convert include over to SRCTOPUse SRCTOP in place of .CURDIR/.. as appropriate. The hand-craftedrelative paths for the "links" option remain, though, since those arerelative to /usr/include/sys/ not to the source tree.Differential Revision: https://reviews.freebsd.org/D9932Sponsored by: NetflixSilence On: arch@ (twice) List of files: /freebsd-12.1/include/Makefile

9622c93a - hyperv: Allow userland to ro-mmap reference TSC page

Thu, 15 Dec 2016 03:32:24 +0000

hyperv: Allow userland to ro-mmap reference TSC pageThis paves way to implement VDSO for the enlightened time counter.Reviewed by: kibMFC after: 1 weekSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8768 List of files: /freebsd-12.1/include/Makefile

34ecf418 - Create the /usr/lib/include symlink as relative.

Sat, 03 Dec 2016 05:29:12 +0000

Create the /usr/lib/include symlink as relative.This ugly code is done to avoid assuming LIBDIR is 2 componentsdeep.Reported by: jhb List of files: /freebsd-12.1/include/Makefile

168fce73 - hyperv/vss: Add driver and tools for VSS

Tue, 15 Nov 2016 02:36:12 +0000

hyperv/vss: Add driver and tools for VSSVSS stands for "Volume Shadow Copy Service". Unlike virtual machinesnapshot, it only takes snapshot for the virtual disks, so bothfilesystem and applications have to aware of it, and cooperate thewhole VSS process.This driver exposes two device files to the userland: /dev/hv_fsvss_dev Normally userland programs should _not_ mess with this device file. It is currently used by the hv_vss_daemon(8), which freezes and thaws the filesystem. NOTE: currently only UFS is supported, if the system mounts _any_ other filesystems, the hv_vss_daemon(8) will veto the VSS process. If hv_vss_daemon(8) was disabled, then this device file must be opened, and proper ioctls must be issued to keep the VSS working. /dev/hv_appvss_dev Userland application can opened this device file to receive the VSS freeze notification, hold the VSS for a while (mainly to flush application data to filesystem), release the VSS process, and receive the VSS thaw notification i.e. applications can run again. The VSS will still work, even if this device file is not opened. However, only filesystem consistency is promised, if this device file is not opened or is not operated properly.hv_vss_daemon(8) is started by devd(8) by default. It can be disabledby editting /etc/devd/hyperv.conf.Submitted by: Hongjiang Zhang Reviewed by: kib, mckusickMFC after: 3 weeksSponsored by: MicrosoftDifferential Revision: https://reviews.freebsd.org/D8224 List of files: /freebsd-12.1/include/Makefile

50875ed2 - Re-apply change 306811 or alternatively, revert change 307385.

Sun, 16 Oct 2016 02:43:51 +0000

Re-apply change 306811 or alternatively, revert change 307385. List of files: /freebsd-12.1/include/Makefile

9ffbf09f - Revert change 306811 so that the change can be re-done using

Sun, 16 Oct 2016 02:05:22 +0000

Revert change 306811 so that the change can be re-done usingsvn copy instead of svn move. This to preserve history onthe originals headers as well. List of files: /freebsd-12.1/include/Makefile

dca5dd68 - install header files required development with libzfs_core

Wed, 12 Oct 2016 07:08:32 +0000

install header files required development with libzfs_corelibzfs_core provides a rather limited but committed (stable) interfacefor working with ZFS. We install libzfs_core shared library but we donot install header files required for developing programs that usethe library. This change is to install the required header fileslibzfs_core.h, libnvpair.h and sys/nvpair.h.The headers are installed into the same locations as on illumos.Reviewed by: mav, markjDifferential Revision: https://reviews.freebsd.org/D8005 List of files: /freebsd-12.1/include/Makefile