tiomap-dev team mailing list archive

[Oliver Grawert <ogra@xxxxxxxxxx>]

i fear for now you have to replace the hardcoded value in the
jasper_setup script with a better hardcoded value ... easiest should be
to just append an overlay file (named jasper_setup) with the same path
to your initrd.

http://wiki.debian.org/DebianInstaller/NetbootFirmware#Squeeze_Example_.231_:_add_single_firmware_deb
shows how you can easily merge 2 cpio archives where one has an overlay.

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/872178

Title:
  ROOTDEV export not working

Status in “jasper-initramfs” package in Ubuntu:
  New

Bug description:
  I am using oneiric pre-installed image for omap4 with jasper 0.66.
  Script jasper_setup is supposed to use "ROOTDEV"environment value exported by jasper_growroot.
  Installing image on Blaze board (with eMMC support) demonstrate that there is an issue with "export ROOTDEV" in  jasper_growroot, the value is not accessible then into jasper_setup
  By adding some traces into jasper_setup (echo "ROOTDEV=${ROOTDEV}" >> /dev/kmsg) we can see that ROOTDEV is not set.
  Installation on Blaze Board is then failing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jasper-initramfs/+bug/872178/+subscriptions