Makefile

OUT := qdl

CFLAGS := -O2 -Wall -g `pkg-config --cflags libxml-2.0`
LDFLAGS := `pkg-config --libs libxml-2.0 libudev`
prefix := /usr/local

SRCS := firehose.c qdl.c sahara.c util.c patch.c program.c ufs.c
OBJS := $(SRCS:.c=.o)

KS_OUT := ks
KS_SRCS := ks.c sahara.c util.c
KS_OBJS := $(KS_SRCS:.c=.o)

default: $(OUT) $(KS_OUT)

$(OUT): $(OBJS)
	$(CC) -o $@ $^ $(LDFLAGS)

$(KS_OUT): $(KS_OBJS)
	$(CC) -o $@ $^ $(LDFLAGS)

clean:
	rm -f $(OUT) $(OBJS)
	rm -f $(KS_OUT) $(KS_OBJS)

install: $(OUT)
	install -D -m 755 $< $(DESTDIR)$(prefix)/bin/$<
qdl: Support for program and patch Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2016-07-08 11:26:26 -07:00			`OUT := qdl`

makefile: Use pkg-config instead of xml2-config Per user request, use pkg-config instead of xml2-config when generating cflags and ldflags. Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2021-11-10 09:44:50 -06:00			CFLAGS := -O2 -Wall -g `pkg-config --cflags libxml-2.0`
			LDFLAGS := `pkg-config --libs libxml-2.0 libudev`
Makefile: implement GNU Coding Standard for Makefiles GNU coding standards notably specifies: * install files with the $(DESTDIR) to the target system image * install files with the $(prefix), not $(PREFIX) * the default value of $(prefix) should be /usr/local as per https://www.gnu.org/prep/standards/html_node/Directory-Variables.html. Suggested-by: Kirill Kapranov <kkapra@codeaurora.org> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2017-11-06 22:55:11 -08:00			`prefix := /usr/local`
qdl: Support for program and patch Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2016-07-08 11:26:26 -07:00
QDL/firehose: Add UFS provisioning functionality Add UFS provisioning functionality using Firehose. Signed-off-by: Kirill Kapranov <kkapra@codeaurora.org> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2018-02-14 23:49:07 +02:00			`SRCS := firehose.c qdl.c sahara.c util.c patch.c program.c ufs.c`
qdl: Support for program and patch Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2016-07-08 11:26:26 -07:00			`OBJS := $(SRCS:.c=.o)`

Add ks utility ks (short for kickstart) is a utility which uses sahara to load images from the host to a device. This is intended for "flashless boot" devices like the Qualcomm Cloud AI 100 which rely on obtaining the runtime firmware from the host instead of storing it on device. While ks uses sahara, like qdl, it is different enough that a separate utility is justified. ks does not need USB support, instead opting for simple open()/read()/write() operations. ks does not need firehose. The set of program arguments that ks needs is vastly different than the set that qdl supports. This initial implementation of ks defines two arguments. Both are required, but the image specifier argument can be specified more than one. A sample invocation - ks -p /dev/mhi0_QAIC_SAHARA -s 1:/opt/qti-aic/firmware/fw1.bin -s 2:/opt/qti-aic/firmware/fw2.bin In this example, ks is instructed to use the /dev/mhi0_QAIC_SAHARA device node file as the "port" which the device is using for the sahara protocol. /opt/qti-aic/firmware/fw1.bin is mapped to id 1, and /opt/qti-aic/firmware/fw2.bin is mapped to id 2. If the device requests image id 1, ks will attempt to open and read /opt/qti-aic/firmware/fw1.bin to send to the device. Note that /opt/qti-aic/firmware/fw1.bin does not need to exist on the filesystem. If ks cannot access the file (perhaps because it does not exist), then the device will determine the next action. This is useful for setting up a single command in a udev rule that can handle multiple configurations, such as an optional DDR training process. Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com> 2023-01-24 17:00:10 +00:00			`KS_OUT := ks`
			`KS_SRCS := ks.c sahara.c util.c`
			`KS_OBJS := $(KS_SRCS:.c=.o)`

			`default: $(OUT) $(KS_OUT)`

qdl: Support for program and patch Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2016-07-08 11:26:26 -07:00			`$(OUT): $(OBJS)`
			`$(CC) -o $@ $^ $(LDFLAGS)`

Add ks utility ks (short for kickstart) is a utility which uses sahara to load images from the host to a device. This is intended for "flashless boot" devices like the Qualcomm Cloud AI 100 which rely on obtaining the runtime firmware from the host instead of storing it on device. While ks uses sahara, like qdl, it is different enough that a separate utility is justified. ks does not need USB support, instead opting for simple open()/read()/write() operations. ks does not need firehose. The set of program arguments that ks needs is vastly different than the set that qdl supports. This initial implementation of ks defines two arguments. Both are required, but the image specifier argument can be specified more than one. A sample invocation - ks -p /dev/mhi0_QAIC_SAHARA -s 1:/opt/qti-aic/firmware/fw1.bin -s 2:/opt/qti-aic/firmware/fw2.bin In this example, ks is instructed to use the /dev/mhi0_QAIC_SAHARA device node file as the "port" which the device is using for the sahara protocol. /opt/qti-aic/firmware/fw1.bin is mapped to id 1, and /opt/qti-aic/firmware/fw2.bin is mapped to id 2. If the device requests image id 1, ks will attempt to open and read /opt/qti-aic/firmware/fw1.bin to send to the device. Note that /opt/qti-aic/firmware/fw1.bin does not need to exist on the filesystem. If ks cannot access the file (perhaps because it does not exist), then the device will determine the next action. This is useful for setting up a single command in a udev rule that can handle multiple configurations, such as an optional DDR training process. Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com> 2023-01-24 17:00:10 +00:00			`$(KS_OUT): $(KS_OBJS)`
			`$(CC) -o $@ $^ $(LDFLAGS)`

qdl: Support for program and patch Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2016-07-08 11:26:26 -07:00			`clean:`
			`rm -f $(OUT) $(OBJS)`
Add ks utility ks (short for kickstart) is a utility which uses sahara to load images from the host to a device. This is intended for "flashless boot" devices like the Qualcomm Cloud AI 100 which rely on obtaining the runtime firmware from the host instead of storing it on device. While ks uses sahara, like qdl, it is different enough that a separate utility is justified. ks does not need USB support, instead opting for simple open()/read()/write() operations. ks does not need firehose. The set of program arguments that ks needs is vastly different than the set that qdl supports. This initial implementation of ks defines two arguments. Both are required, but the image specifier argument can be specified more than one. A sample invocation - ks -p /dev/mhi0_QAIC_SAHARA -s 1:/opt/qti-aic/firmware/fw1.bin -s 2:/opt/qti-aic/firmware/fw2.bin In this example, ks is instructed to use the /dev/mhi0_QAIC_SAHARA device node file as the "port" which the device is using for the sahara protocol. /opt/qti-aic/firmware/fw1.bin is mapped to id 1, and /opt/qti-aic/firmware/fw2.bin is mapped to id 2. If the device requests image id 1, ks will attempt to open and read /opt/qti-aic/firmware/fw1.bin to send to the device. Note that /opt/qti-aic/firmware/fw1.bin does not need to exist on the filesystem. If ks cannot access the file (perhaps because it does not exist), then the device will determine the next action. This is useful for setting up a single command in a udev rule that can handle multiple configurations, such as an optional DDR training process. Signed-off-by: Jeffrey Hugo <quic_jhugo@quicinc.com> 2023-01-24 17:00:10 +00:00			`rm -f $(KS_OUT) $(KS_OBJS)`
Makefile: implement GNU Coding Standard for Makefiles GNU coding standards notably specifies: * install files with the $(DESTDIR) to the target system image * install files with the $(prefix), not $(PREFIX) * the default value of $(prefix) should be /usr/local as per https://www.gnu.org/prep/standards/html_node/Directory-Variables.html. Suggested-by: Kirill Kapranov <kkapra@codeaurora.org> Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org> 2017-11-06 22:55:11 -08:00
			`install: $(OUT)`
			`install -D -m 755 $< $(DESTDIR)$(prefix)/bin/$<`