diff options
Diffstat (limited to 'scripts/upgrade/README')
| -rw-r--r-- | scripts/upgrade/README | 106 |
1 files changed, 49 insertions, 57 deletions
diff --git a/scripts/upgrade/README b/scripts/upgrade/README index 6d5a1b6..c94f72f 100644 --- a/scripts/upgrade/README +++ b/scripts/upgrade/README @@ -1,62 +1,54 @@ The upgrade scripts goes in a tarball with local.conf at the top level. -The tree is a follows: -. -|-- install_list.txt -|-- install_list.txt.md5 -|-- install.sh* -|-- install.sh.md5 -|-- local.conf -|-- local.conf.md5 -|-- model -`-- repo/ - |-- arm926ejste/ - | |-- busybox_1.24.1-r0.mlinux2.mlinux2.1_arm926ejste.ipk - | |-- busybox-hwclock_1.24.1-r0.mlinux2.mlinux2.1_arm926ejste.ipk - | |-- busybox-ifplugd_1.24.1-r0.mlinux2.mlinux2.1_arm926ejste.ipk - | |-- busybox-syslog_1.24.1-r0.mlinux2.mlinux2.1_arm926ejste.ipk - | |-- busybox-udhcpc_1.24.1-r0.mlinux2.mlinux2.1_arm926ejste.ipk - | |-- initscripts_1.0-r155.3.40.0_arm926ejste.ipk - | |-- initscripts-functions_1.0-r155.3.40.0_arm926ejste.ipk - | |-- Packages - | |-- Packages.gz - | `-- Packages.stamps - `-- Packages - - - -install.sh gets executed if it exists by /etc/init.d/umountfs - -The files are placed in a tarball called upgrade.bin, and it -should be located in either /var/volatile/flash-upgrade or -/media/card/flash-upgrade to be compatible with umountfs. - -The file /var/volatile/do_flash_upgrade must exist and -be owned by root for umountfs to execute the upgrade -procedure. - -install_list.txt is a list of packages to -install after the upgrade. If some packages -have mutual dependencies on each other, they should -be put on the same line. +log.txt shows what happens when the package is installed. -The file local.conf should contain a list of -architectures with priorities, and a list of -repositories. - -The md5sums are created as follows: - -cat install.sh | md5sum -c install.sh.md5 -md5sum install.sh >install.sh.md5 -md5sum local.conf >local.conf.md5 - -model is from the part of the hardware -version before the first hyphen. - -Example: - -MTCAP-0.1 Would be MTCAP -MTCDT-0.0 Would be MTCDT -MTCDTIP-0.1 Would be MTCDTIP +The script build.sh is used to create the binary update package +used by mlinux-firmware-update. +The tree is a follows: +upgrade-4.0.0-4.0.1/ +├── install_list.txt +├── local.conf +└── repo + ├── arm926ejste + │ ├── bluez5_5.47-m3.0_arm926ejste.ipk + │ ├── bluez5-noinst-tools_5.47-m3.0_arm926ejste.ipk + │ ├── bluez5-obex_5.47-m3.0_arm926ejste.ipk + │ ├── bluez5-pand_5.47-m3.0_arm926ejste.ipk + │ ├── bluez5-rfcomm_5.47-m3.0_arm926ejste.ipk + │ ├── bluez5-testtools_5.47-m3.0_arm926ejste.ipk + │ ├── libasound-module-bluez_5.47-m3.0_arm926ejste.ipk + │ ├── libmts-io0_1.0.8-r0.0_arm926ejste.ipk + │ ├── lora-network-server_2.0.19-r4.0_arm926ejste.ipk + │ ├── Packages + │ ├── Packages.gz + │ ├── Packages.stamps + │ └── python-pybluez_0.22-r0.0_arm926ejste.ipk + ├── mtcap + │ ├── mlinux-version_4.0.1_ea6ba1e5fb287003fea33522af39a771102713b2-r2.0_mtcap.ipk + │ ├── mts-id-eeprom_0.3.8-r1.0.0_mtcap.ipk + │ ├── Packages + │ ├── Packages.gz + │ └── Packages.stamps + ├── mtcdt + │ ├── mlinux-version_4.0.1_ea6ba1e5fb287003fea33522af39a771102713b2-r2.0_mtcdt.ipk + │ ├── mts-id-eeprom_0.3.8-r1.0.0_mtcdt.ipk + │ ├── Packages + │ ├── Packages.gz + │ └── Packages.stamps + └── Packages + + +If one puts the packages in a build tree at build/tmp/deploy/ipk, +and run bitbake package-index, the Packages* files are refreshed. + +In this example, all MTCDT-like models as of today are supported. + +That is MTCDT, MTCDTIP, MTCDTIPHP, and MTCAP are supported in this +update. + +install_list.txt would be a list of extra packages to install. + +We should probably have a remove_list.txt for cases where packages +are obsolete. |