branches with status:
Name Status Last Modified Last Commit
lp:~berolinux/linaro-image-tools/mx6qsabrelite-bootargs bug(Has a merge proposal) 1 Development 2012-03-01 08:57:24 UTC 2012-03-01
497. Use the right bootargs for MX6QSabrel...

Author: Bernhard Rosenkraenzer
Revision Date: 2012-02-29 14:26:14 UTC

Use the right bootargs for MX6QSabrelite

lp:~berolinux/linaro-image-tools/android-iMX53 (Has a merge proposal) 1 Development 2011-07-25 00:17:48 UTC 2011-07-25
388. Assorted i.MX53 (and related) fixes: ...

Author: Bernhard Rosenkraenzer
Revision Date: 2011-07-25 00:13:53 UTC

Assorted i.MX53 (and related) fixes:
- boot loader partition is needed
- Don't barf in linaro-android-media-create if mmc_part_offset is 1
- install boot loader on SD card

lp:~berolinux/linaro-image-tools/fix-linaro-android-media-create (Has a merge proposal) 1 Development 2011-07-23 22:27:08 UTC 2011-07-23
387. Fix linaro-android-media-create after...

Author: Bernhard Rosenkraenzer
Revision Date: 2011-07-23 22:22:58 UTC

Fix linaro-android-media-create after recent mount/umount changes

Without this, this traceback occurs:
mkfs.vfat 3.0.11 (24 Dec 2010)
mount: /dev/mmcblk0p1 already mounted or /tmp/tmp18MYEP/boot-disc busy
mount: according to mtab, /dev/mmcblk0p1 is already mounted on /tmp/tmp18MYEP/boot-disc
Traceback (most recent call last):
  File "./linaro-android-media-create", line 144, in <module>
    board_config.populate_boot_script(boot_partition, BOOT_DISK, args.consoles)
  File "/usr/src/repos/linaro/linaro-image-tools/linaro_image_tools/media_create/android_boards.py", line 82, in populate_boot_script
    as_root=True).wait()
  File "/usr/src/repos/linaro/linaro-image-tools/linaro_image_tools/cmd_runner.py", line 100, in wait
    raise SubcommandNonZeroReturnValue(self._my_args, returncode)
linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process "['mount', '/dev/mmcblk0p1', '/tmp/tmp18MYEP/boot-disc']" returned a non-zero value: 32

The problem is that linaro-android-media-create assumes
populate_partition(... BOOT_DISK ...)
unmounts the boot filesystem after running (no longer true).

Furthermore, board_config.populate_boot_script used to umount
the boot filesystem, causing the umount in the atexit handler to fail.

13 of 3 results