]> code.ossystems Code Review - openembedded-core.git/commit
wic: sdimage-bootpart: Use mmcblk0 drive instead of bogus mmcblk
authorAlexey Brodkin <alexey.brodkin@synopsys.com>
Wed, 16 Jan 2019 08:27:19 +0000 (11:27 +0300)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 16 Jan 2019 11:10:09 +0000 (11:10 +0000)
commit57a925dbd949e488980b02896106efd82bf47ed2
tree2c164b964a1957230bea176ec2525a4e32a06795
parent8e3311d45ec68d74e934e966f67cf5102634981c
wic: sdimage-bootpart: Use mmcblk0 drive instead of bogus mmcblk

Apparently either nobody ever used sdimage-bootpart.wks
or fstab was kept untouched due to "--no-fstab-update" usage as
some boards like IMX may have, see [1].

Otherwise addition of the following line to the target's fstab:
---------------------->8-----------------
/dev/mmcblkp1   /boot   vfat    defaults        0       0
---------------------->8-----------------

gets us unusable target:
---------------------->8-----------------
[*     ] A start job is running for dev-mmcblkp1.device (23s / 1min 30s)
[ TIME ] Timed out waiting for device dev-mmcblkp1.device.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or "exit"
to boot into default mode.
Press Enter for maintenance
---------------------->8-----------------

Fix it with use of "mmcblk0" device name.

[1] https://lists.yoctoproject.org/pipermail/meta-freescale/2018-February/022156.html

Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Cc: Maciej Borzecki <maciej.borzecki@open-rnd.pl>
Cc: Maciek Borzecki <maciek.borzecki@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
scripts/lib/wic/canned-wks/sdimage-bootpart.wks