bcm53xx: use otrx for creating TRX images

The advantage is that we don't have to specify max TRX size anymore and
otrx doesn't allocate a buffer of that size. It saves us allocating
32 MiB for every image we generate.

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
This commit is contained in:
Rafał Miłecki 2017-11-17 11:43:33 +01:00
parent fb66dc9b03
commit 370ce1fb48

View File

@ -59,9 +59,7 @@ define Build/trx
endef endef
define Build/trx-serial define Build/trx-serial
$(STAGING_DIR_HOST)/bin/trx \ $(STAGING_DIR_HOST)/bin/otrx create $@.new \
-o $@.new \
-m 33554432 \
-f $(IMAGE_KERNEL) -a 1024 \ -f $(IMAGE_KERNEL) -a 1024 \
-f $@ -a 0x10000 -A $(KDIR)/fs_mark -f $@ -a 0x10000 -A $(KDIR)/fs_mark
mv $@.new $@ mv $@.new $@
@ -72,9 +70,7 @@ define Build/trx-nand
# if it grows up between releases # if it grows up between releases
# root: UBI with one extra block containing UBI mark to trigger erasing # root: UBI with one extra block containing UBI mark to trigger erasing
# rest of partition # rest of partition
$(STAGING_DIR_HOST)/bin/trx \ $(STAGING_DIR_HOST)/bin/otrx create $@.new \
-o $@.new \
-m 33554432 \
-f $(IMAGE_KERNEL) -a 0x20000 -b 0x400000 \ -f $(IMAGE_KERNEL) -a 0x20000 -b 0x400000 \
-f $@ \ -f $@ \
-A $(KDIR)/ubi_mark -a 0x20000 -A $(KDIR)/ubi_mark -a 0x20000