<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/include/configs, branch v2017.11-rc1</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/include/configs?h=v2017.11-rc1</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/include/configs?h=v2017.11-rc1'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2017-09-30T22:33:34Z</updated>
<entry>
<title>evb-rk3399: avoid redefinition of CONFIG_ENV_OFFSET</title>
<updated>2017-09-30T22:33:34Z</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>xypron.glpk@gmx.de</email>
</author>
<published>2017-09-27T18:23:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=861ff277575fb00c8b8d22c3baab726c353a8fea'/>
<id>urn:sha1:861ff277575fb00c8b8d22c3baab726c353a8fea</id>
<content type='text'>
CONFIG_ENV_OFFSET is already defined in
include/configs/rockchip-common.h

For CONFIG_ROCKCHIP_BACK_TO_BROM=y we redefine CONFIG_ENV_OFFSET
to an unsuitable value. We were lucky to get a compiler warning.

Remove the incorrect redefinition.

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Acked-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
Reviewed-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
</content>
</entry>
<entry>
<title>rk3288: vyasa: Add falcon mode support</title>
<updated>2017-09-30T22:33:33Z</updated>
<author>
<name>Jagan Teki</name>
<email>jagan@amarulasolutions.com</email>
</author>
<published>2017-09-27T17:33:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5d94ebedcd192bcceabcd1ca90f417f1130e46dc'/>
<id>urn:sha1:5d94ebedcd192bcceabcd1ca90f417f1130e46dc</id>
<content type='text'>
Add Falcon mode support in vyasa rk3288 board.

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
Acked-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
</content>
</entry>
<entry>
<title>rk3288: vyasa: Add TPL support</title>
<updated>2017-09-30T22:33:33Z</updated>
<author>
<name>Jagan Teki</name>
<email>jagan@amarulasolutions.com</email>
</author>
<published>2017-09-27T17:33:12Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=532cb7f5ada0cc3779c33606d760ec99f6aa847a'/>
<id>urn:sha1:532cb7f5ada0cc3779c33606d760ec99f6aa847a</id>
<content type='text'>
Since the size of SPL can't be exceeded 0x8000 bytes in RK3288,
it is not possible add new SPL features like Falcon mode or etc.

So add TPL stage so-that adding new features to SPL is possible.
- TPL: DRAM init, clocks
- SPL: MMC, falcon, etc

Signed-off-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
Reviewed-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
Acked-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
</content>
</entry>
<entry>
<title>arm: dra7xx: Fix Linux boot from eMMC</title>
<updated>2017-09-29T18:07:58Z</updated>
<author>
<name>Sam Protsenko</name>
<email>semen.protsenko@linaro.org</email>
</author>
<published>2017-09-21T19:37:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a0b0ff0ae643b77a3c40bfa87dc2ffa964b4371a'/>
<id>urn:sha1:a0b0ff0ae643b77a3c40bfa87dc2ffa964b4371a</id>
<content type='text'>
Right now on OMAP5-based boards we have only one partition defined for
Linux boot, which is rootfs. That doesn't work with bootpart=1:2 (that
is defined in include/environment/ti/boot.h). To fix Linux boot we may
either:

 1. Change bootpart to be 1:1
 2. Or add preceding partition, so that rootfs is actually 1:2

Second choice seems more reasonable, as DFU is already using similar
partition table and can rely on bootpart to be 1:2.

This patch adds "bootloader" partition. So now eMMC layout for Linux
boot looks like this:

offset               content                 size          partition
(KiB)                                        (KiB)
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;

=======================================================================

0       +--------------------------------+
        | MBR/GPT header                 |   128           -
128     +--------------------------------+
        | MLO                            |   256           -
384     +--------------------------------+
        | u-boot.img                     |   1792          bootloader
2176    +--------------------------------+
        | //////////// hole //////////// |   256           -
2432    +--------------------------------+
        | U-Boot environment             |   128           -
2560    +--------------------------------+
        | U-Boot environment (redundant) |   128           -
2688    +--------------------------------+
        | rootfs                         |   remaining     rootfs
end     +--------------------------------+

=======================================================================

Guard hole appears because U-Boot environment offset was calculated for
Android partition table, which has two additional partitions in place of
that hole ("environment" and "misc" partitions).

This patch also changes rootfs offset from 2 MiB further to 2688 KiB,
so that there won't be any collisions with U-Boot environment when we
flash rootfs.

Signed-off-by: Sam Protsenko &lt;semen.protsenko@linaro.org&gt;
</content>
</entry>
<entry>
<title>arm: am57xx: Fix Linux boot from eMMC</title>
<updated>2017-09-29T18:07:57Z</updated>
<author>
<name>Sam Protsenko</name>
<email>semen.protsenko@linaro.org</email>
</author>
<published>2017-09-21T19:37:56Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f6d245b8c56c8188cef884a45de7fd714c940cad'/>
<id>urn:sha1:f6d245b8c56c8188cef884a45de7fd714c940cad</id>
<content type='text'>
Right now on OMAP5-based boards we have only one partition defined for
Linux boot, which is rootfs. That doesn't work with bootpart=1:2 (that
is defined in include/environment/ti/boot.h). To fix Linux boot we may
either:

 1. Change bootpart to be 1:1
 2. Or add preceding partition, so that rootfs is actually 1:2

Second choice seems more reasonable, as DFU is already using similar
partition table and can rely on bootpart to be 1:2.

This patch adds "bootloader" partition. So now eMMC layout for Linux
boot looks like this:

offset               content                 size          partition
(KiB)                                        (KiB)
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;

=======================================================================

0       +--------------------------------+
        | MBR/GPT header                 |   128           -
128     +--------------------------------+
        | MLO                            |   256           -
384     +--------------------------------+
        | u-boot.img                     |   1792          bootloader
2176    +--------------------------------+
        | //////////// hole //////////// |   256           -
2432    +--------------------------------+
        | U-Boot environment             |   128           -
2560    +--------------------------------+
        | U-Boot environment (redundant) |   128           -
2688    +--------------------------------+
        | rootfs                         |   remaining     rootfs
end     +--------------------------------+

=======================================================================

Guard hole appears because U-Boot environment offset was calculated for
Android partition table, which has two additional partitions in place of
that hole ("environment" and "misc" partitions).

This patch also changes rootfs offset from 2 MiB further to 2688 KiB,
so that there won't be any collisions with U-Boot environment when we
flash rootfs.

Signed-off-by: Sam Protsenko &lt;semen.protsenko@linaro.org&gt;
</content>
</entry>
<entry>
<title>configs: keystone2: env: Fix burn_uboot_spi command</title>
<updated>2017-09-29T18:07:56Z</updated>
<author>
<name>Lokesh Vutla</name>
<email>lokeshvutla@ti.com</email>
</author>
<published>2017-09-21T02:01:13Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ba7f58b12f48212085d5c26c84b6e13cdb30c1f4'/>
<id>urn:sha1:ba7f58b12f48212085d5c26c84b6e13cdb30c1f4</id>
<content type='text'>
Now the u-boot spi image is greater than 0x80000, increase the same
in env during spi erase.

Reported-by: Yan Liu &lt;yan-liu@ti.com&gt;
Signed-off-by: Lokesh Vutla &lt;lokeshvutla@ti.com&gt;
</content>
</entry>
<entry>
<title>configs: k2g_evm: Make findfdt command populate fdtfile variable</title>
<updated>2017-09-29T18:07:56Z</updated>
<author>
<name>Andrew F. Davis</name>
<email>afd@ti.com</email>
</author>
<published>2017-09-20T19:45:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f8e714ebfa6f225a2eaca1d7be9e6963801fe762'/>
<id>urn:sha1:f8e714ebfa6f225a2eaca1d7be9e6963801fe762</id>
<content type='text'>
On all other platforms the command 'findfdt' populates the variable
'fdtfile', but on K2G we only populate 'name_fdt'. The generic boot
and automation scripts fail when 'findfdt' is not populated, fix
this for K2G.

Signed-off-by: Andrew F. Davis &lt;afd@ti.com&gt;
</content>
</entry>
<entry>
<title>configs: am43xx_evm: Avoid relocation onto firewall at the end of DRAM</title>
<updated>2017-09-29T18:07:55Z</updated>
<author>
<name>Andrew F. Davis</name>
<email>afd@ti.com</email>
</author>
<published>2017-09-20T19:38:50Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=373358f27ad4960480e63e6445bca2a5fd089479'/>
<id>urn:sha1:373358f27ad4960480e63e6445bca2a5fd089479</id>
<content type='text'>
On secure devices the initial secure software may install a firewall at
the end of DRAM, define protected RAM to avoid space.

Signed-off-by: Andrew F. Davis &lt;afd@ti.com&gt;
</content>
</entry>
<entry>
<title>ARM: omap3: am3517-evm: Add device tree and DM support</title>
<updated>2017-09-29T18:07:54Z</updated>
<author>
<name>Adam Ford</name>
<email>aford173@gmail.com</email>
</author>
<published>2017-09-20T01:32:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b85781c2a82ff33a65a32b64599416d3c21eeba6'/>
<id>urn:sha1:b85781c2a82ff33a65a32b64599416d3c21eeba6</id>
<content type='text'>
With the device tree ported from Linux 4.13, this enables
Driver Model and Device Tree support for the am3517-evm

Signed-off-by: Adam Ford &lt;aford173@gmail.com&gt;
Tested-by: Derald D. Woods &lt;woods.technical@gmail.com&gt;
</content>
</entry>
<entry>
<title>ARM: da850-evm: Enable DM_I2C</title>
<updated>2017-09-29T18:07:18Z</updated>
<author>
<name>Adam Ford</name>
<email>aford173@gmail.com</email>
</author>
<published>2017-09-18T01:43:48Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c774207f48585544664bd9675c14a7812ecce348'/>
<id>urn:sha1:c774207f48585544664bd9675c14a7812ecce348</id>
<content type='text'>
With DM now enabled with the device tree pulled from Linux, we can
enable DM_I2C in U-Boot.

Reviewed-by: Jagan Teki &lt;jagan@openedev.com&gt;
Signed-off-by: Adam Ford &lt;aford173@gmail.com&gt;
[trini: Add DM_I2C_COMPAT to da850_am18xxevm to fix warning]
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
