toolchain: revise Makefile for container builds

Use podman primarily. Default to using the fully qualified image from
ghcr.io

Signed-off-by: Daniel Lublin <daniel@lublin.se>

contrib/Makefile

@@ -18,22 +18,28 @@ all:
 	@echo "docker-build-image    Build a toolchain image named '$(BUILDIMAGE)' (Docker)"
 
 run:
-	./podman-run $(IMAGE) / /usr/bin/bash
+	podman run --rm --mount type=bind,source="`pwd`/../",target=/build -w /build -it \
+	 $(IMAGE) /usr/bin/bash
 
 docker-run:
-	docker run --rm --mount type=bind,source="`pwd`/../",target=/build -w /build -it $(IMAGE) /usr/bin/bash
+	docker run --rm --mount type=bind,source="`pwd`/../",target=/build -w /build -it \
+	 $(IMAGE) /usr/bin/bash
 
 run-make:
-	./podman-run-make $(IMAGE) clean application_fpga.bin
+	podman run --rm --mount type=bind,source="`pwd`/../hw/application_fpga",target=/build -w /build -it \
+	 $(IMAGE) make clean application_fpga.bin
 
 run-make-testfw:
-	./podman-run-make $(IMAGE) clean application_fpga_testfw.bin
+	podman run --rm --mount type=bind,source="`pwd`/../hw/application_fpga",target=/build -w /build -it \
+	 $(IMAGE) make clean application_fpga_testfw.bin
 
 run-make-no-clean:
-	./podman-run-make $(IMAGE) application_fpga.bin
+	podman run --rm --mount type=bind,source="`pwd`/../hw/application_fpga",target=/build -w /build -it \
+	 $(IMAGE) make application_fpga.bin
 
 run-make-clean_fw:
-	./podman-run-make $(IMAGE) clean_fw application_fpga.bin
+	podman run --rm --mount type=bind,source="`pwd`/../hw/application_fpga",target=/build -w /build -it \
+	 $(IMAGE) make clean_fw application_fpga.bin
 
 pull:
 	podman pull $(IMAGE)

doc/framing_protocol/framing_protocol.md

@@ -114,10 +114,10 @@ The bits in the command header byte should be interpreted as:
 * Bits [6..5] (2 bits). Frame ID tag.
 
 * Bits [4..3] (2 bits). Endpoint number.
-0. HW in interface_fpga
+0. HW in interface_fpga (unused)
 1. HW in application_fpga
 2. FW in application_fpga
-3. SW (application) in application_fpga
+3. SW (device application) in application_fpga
 
 * Bit [2] (1 bit). Unused. MUST be zero.
 
@@ -166,10 +166,10 @@ The bits in the response header byte should be interpreted as:
 * Bits [6..5] (2 bits). Frame ID tag.
 
 * Bits [4..3] (2 bits). Endpoint number.
-0. HW in interface_fpga
+0. HW in interface_fpga (unused)
 1. HW in application_fpga
 2. FW in application_fpga
-3. SW (application) in application_fpga
+3. SW (device application) in application_fpga
 
 * Bit [2] (1 bit). Response status.
 0. OK