linux/meta-updater.git, branch feat/rpi4Mirror of github.com/advancedtelematic/meta-updaterhttps://git.enea.com/cgit/linux/meta-updater.git/atom?h=feat%2Frpi42019-09-17T16:00:34+00:00Use the recommended kernel entry point on RPI2019-09-17T16:00:34+00:00Laurent Bonnanslaurent.bonnans@here.com2019-09-17T16:00:34+00:00urn:sha1:2a49666b8a2bbe45f306905a53fd97a80bf5e3d4
0x8000 does not work on raspberrypi4-64 whereas 0x80000 is the value
recommended for all platforms on u-boot
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
Raspberrypi4 initial support2019-09-17T13:55:33+00:00Laurent Bonnanslaurent.bonnans@here.com2019-09-05T14:59:18+00:00urn:sha1:5296877819e156e5006946cc6f626908057172d1
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
Merge pull request #600 from advancedtelematic/fix/initramfs-no-manifest2019-09-11T08:52:51+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-11T08:52:51+00:00urn:sha1:5bfdcc20f2babfc833101b8ce6478eaec86d9b61
Don't try to put the repo manifest in the initramfs image.Merge pull request #589 from advancedtelematic/refactor/uptane-generator-rename2019-09-11T08:32:38+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-11T08:32:38+00:00urn:sha1:af645d5b70f0162c774e3b2b2697f5345725531b
aktualizr: aktualizr-repo was renamed to uptane-generator.aktualizr: aktualizr-repo was renamed to uptane-generator.2019-09-10T15:22:21+00:00Patrick Vacekpatrickvacek@gmail.com2019-08-19T11:45:31+00:00urn:sha1:61c000cf5ca63ed9fda3043fa33c869ad903e504
Also bump to 2019.7 release of aktualizr and latest garage-sign.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Merge pull request #599 from advancedtelematic/feat/better-overlays2019-09-10T12:10:16+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-10T12:10:16+00:00urn:sha1:5348b146054e7b16dff71ceb41697157488867e7
Feat/better overlaysDon't try to put the repo manifest in the initramfs image.2019-09-09T15:06:02+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-09T15:06:02+00:00urn:sha1:506edc97f72440066b6be42ced01ece8390ea499
It isn't very useful there and just takes up space.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Print usage information after parameter checking.2019-09-09T13:34:02+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-09T12:32:44+00:00urn:sha1:357c65d44135b560b25e86ec33b1c1efccb0c7fa
No use printing all that if there's a problem anyway.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Prevent creating an overlay with any path but the current directory.2019-09-09T13:33:26+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-09T12:31:40+00:00urn:sha1:90b3f43885c7a1b68766cbea6b19e4ce40e3f79d
Anything else will cause problems because of the hackery with keeping
backup copies of the image and the u-boot rom.
Also warn about supplying a different image name after the overlay has
been created. That doesn't work and it will be ignored.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Copy the image and U-Boot rom when using overlays.2019-09-06T14:42:37+00:00Patrick Vacekpatrickvacek@gmail.com2019-09-06T14:42:37+00:00urn:sha1:e06640f8f1170ad868db3ecb1af9ff1d2f60c1a2
Since bitbake can remove old images that an overlay was non-obviously
dependent on, the safest thing to do is make a copy of the image and
keep it alongside the overlay. When using the overlay later,
automatically use that image. Also do the same thing with the U-Boot
rom. This should also make moving the overlay file to another machine
much easier.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>