[meta-intel] [meta-intel-galileo] [PATCH 0/3] Fixing launcher.sh running background tasks on non-Galileo platforms

rebecca.swee.fun.chang at intel.com rebecca.swee.fun.chang at intel.com
Thu Apr 30 04:32:08 PDT 2015


From: Chang Rebecca Swee Fun <rebecca.swee.fun.chang at intel.com>

I'm sending this patch set on behalf on Josef while he is away.

The launcher.sh background task is running on non-Galileo platforms
when booted from SD cards. The launcher.sh attempts to load cloader
every 200ms and should only run on Galileo Gen1 and Gen2. The launcher.sh
consumes approx. 5% of CPU usage.

The root cause is wrong entry point for Galileo services in the systemd
scenario.
SPI boot (using init) correctly calls into galileod.sh entry point while
mass storage boot (using systemd) instead wrongly calls straight into
launcher.sh, which is why clloader is run unconditionally on every board.

The implication is that clloader acquires the USB serial gadget
/dev/ttyGS0. The workaround is to kill the launcher.sh process.
This will cause clloader child to terminate and release the gadget serial.

Regards,
Rebecca

Josef Ahmad (3):
  galileod.sh: do not kick off the sketch reset daemon
  launcher.sh: start clloader only on galileo
  launcher.sh: kick off sketch reset binary in background

 recipes-core/initscripts/files/galileod.sh       |  5 ----
 recipes-galileo/galileo-target/files/launcher.sh | 37 +++++++++++++++++++-----
 2 files changed, 30 insertions(+), 12 deletions(-)

-- 
1.9.1



More information about the meta-intel mailing list