freebsd-dev/sbin/camcontrol/Makefile

# $FreeBSD$

.include <src.opts.mk>

PACKAGE=runtime
PROG=	camcontrol
SRCS=	camcontrol.c util.c
SRCS+=	attrib.c depop.c epc.c fwdownload.c modeedit.c persist.c progress.c timestamp.c zone.c
.if ${MK_NVME} != "no"
.PATH:	${SRCTOP}/sbin/nvmecontrol
CFLAGS+= -I${SRCTOP}/sbin/nvmecontrol -DWITH_NVME
SRCS+=	identify_ext.c nc_util.c
.PATH:	${SRCTOP}/sys/dev/nvme
SRCS+=	nvme_util.c
.endif
# This is verboten
.if ${MACHINE_CPUARCH} == "arm"
WARNS?= 3
.endif
LIBADD=	cam sbuf util
MAN=	camcontrol.8

.include <bsd.prog.mk>
Specify the system directory for which we put in our include path as a separate line so we can override it on the command line if we need to. Reviewed by: ken@freebsd.org 2000-01-21 23:18:08 +00:00			`# $FreeBSD$`
Add a MAINTAINER line to modules that I maintain. Suggested by: brian, markm 1999-06-18 00:41:47 +00:00
NVME support is only for x86 and powerpc64. Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme. This should fix the newly introduced nvme files to camcontrol which were building everywhere. Pointy Hat To: imp Sponsored by: Netflix 2018-06-14 01:15:19 +00:00			`.include <src.opts.mk>`

Explicitly add more files to the 'runtime' package. Sponsored by: The FreeBSD Foundation 2016-02-09 20:19:31 +00:00			`PACKAGE=runtime`
Style. Approved by: ken 2002-01-24 16:53:08 +00:00			`PROG= camcontrol`
Fix build when RELEASE_CRUNCH is defined. 2012-01-29 09:12:34 +00:00			`SRCS= camcontrol.c util.c`
camcontrol: depop command Implement and document the new depop command. This command manages drive elements for drives that support it. Storage elements are typically heads. Element status can be discovered. Elements may be removed or restored. And the status of any current depop operation can be assessed. depop -d elm will remove element elm and truncate available capacity. depop -l will list the current drive elements and their current status. depop -r elm will try to restore all retired elements and rebuild capacity. Changing storage elements may reinitialize the drive. This operation will lose data and may take hours to complete. Use the drive provided timeout for operations by default. Reviewed by: gbe (manpages) Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D29018 2021-09-17 22:30:06 +00:00			`SRCS+= attrib.c depop.c epc.c fwdownload.c modeedit.c persist.c progress.c timestamp.c zone.c`
NVME support is only for x86 and powerpc64. Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme. This should fix the newly introduced nvme files to camcontrol which were building everywhere. Pointy Hat To: imp Sponsored by: Netflix 2018-06-14 01:15:19 +00:00			`.if ${MK_NVME} != "no"`
Make camcontrol identify work with nda devices Both ATA and NVME have an identify command. They are completely different, but to the user they are the same. Leverage nvmecontrol's print_controller code to provide that functionality to camcontrol identify. Query the path to see what kind of protocol it supports, and send the most appropriate command down. Refactor nvme_print_dev a little to make it easy to get the nvme cdata. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D15371 2018-06-13 22:00:08 +00:00			`.PATH: ${SRCTOP}/sbin/nvmecontrol`
NVME support is only for x86 and powerpc64. Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme. This should fix the newly introduced nvme files to camcontrol which were building everywhere. Pointy Hat To: imp Sponsored by: Netflix 2018-06-14 01:15:19 +00:00			`CFLAGS+= -I${SRCTOP}/sbin/nvmecontrol -DWITH_NVME`
Make camcontrol identify work with nda devices Both ATA and NVME have an identify command. They are completely different, but to the user they are the same. Leverage nvmecontrol's print_controller code to provide that functionality to camcontrol identify. Query the path to see what kind of protocol it supports, and send the most appropriate command down. Refactor nvme_print_dev a little to make it easy to get the nvme cdata. Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D15371 2018-06-13 22:00:08 +00:00			`SRCS+= identify_ext.c nc_util.c`
			`.PATH: ${SRCTOP}/sys/dev/nvme`
			`SRCS+= nvme_util.c`
NVME support is only for x86 and powerpc64. Implement MK_NVME now that the expression for where NVMe is complicated. Default it to "yes" for x86 and powerpc64 and no everywhere else. Use it in camcontrol to define WITH_NVME for those platforms where we support nvme. This should fix the newly introduced nvme files to camcontrol which were building everywhere. Pointy Hat To: imp Sponsored by: Netflix 2018-06-14 01:15:19 +00:00			`.endif`
MFtbemd: Prefer MACHNE_CPUARCH to MACHINE_ARCH in most contexts where you want to test of all the CPUs of a given family conform. 2010-08-23 22:24:11 +00:00			`# This is verboten`
			`.if ${MACHINE_CPUARCH} == "arm"`
Use WARNS?=3 for these in the arm case for now, due to toolchain issues. 2004-05-14 13:31:21 +00:00			`WARNS?= 3`
			`.endif`
Convert sbin/ to LIBADD Reduce overlinking 2014-11-25 11:23:12 +00:00			`LIBADD= cam sbuf util`
Style. Approved by: ken 2002-01-24 16:53:08 +00:00			`MAN= camcontrol.8`
Camcontrol - A utility for configuring/manipulating the CAM subsystem Submitted by: "Kenneth D. Merry" <ken@plutotech.com> 1998-09-15 06:43:02 +00:00
			`.include <bsd.prog.mk>`