<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-freescale.git/wic/imx-uboot-mxs.wks.in, branch topic/secure-boot</title>
<subtitle>Mirror of github.com/Freescale/meta-freescale</subtitle>
<id>https://git.enea.com/cgit/linux/meta-freescale.git/atom?h=topic%2Fsecure-boot</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-freescale.git/atom?h=topic%2Fsecure-boot'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/'/>
<updated>2018-09-26T17:55:29+00:00</updated>
<entry>
<title>image_types_fsl.bbclass: Use IMAGE_LINK_NAME for mxs binaries</title>
<updated>2018-09-26T17:55:29+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2018-07-03T22:13:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=d2bff417fa7953303f3111731638f8c0d2336510'/>
<id>urn:sha1:d2bff417fa7953303f3111731638f8c0d2336510</id>
<content type='text'>
The binary is generated as part of the image build so it should use
the same naming schema to provide consistency. This also fixes the wks
templates which use it.

Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
<entry>
<title>wic: Fix image generation for i.MX MXS SoC family</title>
<updated>2018-07-03T21:41:08+00:00</updated>
<author>
<name>Otavio Salvador</name>
<email>otavio@ossystems.com.br</email>
</author>
<published>2018-04-26T16:52:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-freescale.git/commit/?id=ecdd93874f434fc200c811392cc83f255f26a4c9'/>
<id>urn:sha1:ecdd93874f434fc200c811392cc83f255f26a4c9</id>
<content type='text'>
The image needs to use the U-Boot generated, for the uSD card, so a
dependency on that must be added to ensure the file is available prior
'wic' uses it.

Besides that, the fstype needs to be changed so it sets the partition
mark allowing the bootrom to find it.

Signed-off-by: Otavio Salvador &lt;otavio@ossystems.com.br&gt;
</content>
</entry>
</feed>
