<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/Kconfig, branch v2023.07</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/Kconfig?h=v2023.07</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/Kconfig?h=v2023.07'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2023-05-06T09:28:18Z</updated>
<entry>
<title>include: fdtdec: decouple fdt_addr_t and phys_addr_t size</title>
<updated>2023-05-06T09:28:18Z</updated>
<author>
<name>Johan Jonker</name>
<email>jbx6244@gmail.com</email>
</author>
<published>2023-03-13T00:33:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=53c5093b2ec08c69b48183e23c5ada3c385053e1'/>
<id>urn:sha1:53c5093b2ec08c69b48183e23c5ada3c385053e1</id>
<content type='text'>
The DT specification supports CPUs with both 32-bit and 64-bit addressing
capabilities. In U-boot the fdt_addr_t and phys_addr_t size are coupled
by a typedef. The MTD NAND drivers for 32-bit CPU's can describe partitions
with a 64-bit reg property. These partitions synced from Linux end up with
the wrong offset and sizes when only the lower 32-bit is passed.
Decouple the fdt_addr_t and phys_addr_t size as they don't necessary
match.

Signed-off-by: Johan Jonker &lt;jbx6244@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Kever Yang &lt;kever.yang@rock-chips.com&gt;
</content>
</entry>
<entry>
<title>Kconfig: Remove an impossible condition</title>
<updated>2023-04-28T00:32:05Z</updated>
<author>
<name>Samuel Holland</name>
<email>samuel@sholland.org</email>
</author>
<published>2023-01-22T17:23:51Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=25bc7bfc30532098d9207783ff2ca45cdc5a0161'/>
<id>urn:sha1:25bc7bfc30532098d9207783ff2ca45cdc5a0161</id>
<content type='text'>
ARCH_SUNXI selects BINMAN, so the condition "!BINMAN &amp;&amp; ARCH_SUNXI"
is impossible to satisfy.

Signed-off-by: Samuel Holland &lt;samuel@sholland.org&gt;
Acked-by: Andre Przywara &lt;andre.przywara@arm.com&gt;
Signed-off-by: Andre Przywara &lt;andre.przywara@arm.com&gt;
</content>
</entry>
<entry>
<title>xen: Add dependency on armv8</title>
<updated>2023-04-25T19:31:28Z</updated>
<author>
<name>Michal Simek</name>
<email>michal.simek@amd.com</email>
</author>
<published>2023-04-18T12:51:55Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=539486787ec8bd9337c497171ff8bd67625a51a9'/>
<id>urn:sha1:539486787ec8bd9337c497171ff8bd67625a51a9</id>
<content type='text'>
U-Boot currently implements hypervisor calls only for ARM64 that's why add
dependency on ARM64. The hardware functionality is also available on
ARMv7a, but currently not supported by U-Boot, hence it is not added to the
list of dependencies here.

Signed-off-by: Michal Simek &lt;michal.simek@amd.com&gt;
</content>
</entry>
<entry>
<title>xen: Fix Kconfig dependencies</title>
<updated>2023-04-25T19:31:28Z</updated>
<author>
<name>Michal Simek</name>
<email>michal.simek@amd.com</email>
</author>
<published>2023-04-06T08:04:15Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=44cd761ad665f38f87f064ed0df5c013ec5f88cb'/>
<id>urn:sha1:44cd761ad665f38f87f064ed0df5c013ec5f88cb</id>
<content type='text'>
XEN config can be enabled by other platforms (even it doesn't need to make
sense) that's why fix dependencies. XEN (xenbus.c) requires sscanf (also
pvblock needs it). And PVBLOCK is inside drivers/xen folder which requires
XEN to be enabled.

Signed-off-by: Michal Simek &lt;michal.simek@amd.com&gt;
Reviewed-by: Heinrich Schuchardt &lt;heinrich.schuchardt@canonical.com&gt;
</content>
</entry>
<entry>
<title>ARM: rmobile: Add R-Car Generation 4 support</title>
<updated>2023-04-07T12:33:46Z</updated>
<author>
<name>Hai Pham</name>
<email>hai.pham.ud@renesas.com</email>
</author>
<published>2023-02-28T21:22:03Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5a3b074255df037c10e02ce1134a1b605cf7611f'/>
<id>urn:sha1:5a3b074255df037c10e02ce1134a1b605cf7611f</id>
<content type='text'>
This adds R-Car Generation 4 (Gen4) support as Renesas ARM64 SoC.

In this version, reusing R-Car Gen3 lowlevel initialize routine [1]
and R-Car Gen3 memory map tables [2] .

[1] arch/arm/mach-rmobile/lowlevel_init_gen3.S
[2] arch/arm/mach-rmobile/memmap-gen3.c

Reviewed-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
Signed-off-by: Hai Pham &lt;hai.pham.ud@renesas.com&gt;
Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
[Marek: - Enable DTO support by default
        - Sort the Kconfig lists
	- Select RCAR_64 Kconfig option to pull in all the shared
	  Kconfig options with Gen3, and use where applicable to
	  deduplicate entries.
	- Fix reference [2] typo in commit message
	- Drop config options moved to Kconfig, rename rest to CFG_
	  accordingly to synchronize with upstream changes. Drop
	  removed CONFIG_VERY_BIG_RAM.
        - Move board size limit to arch/Kconfig
	- Move GICR_BASE to headers instead of common config]
</content>
</entry>
<entry>
<title>api: move API related config options into submenu</title>
<updated>2023-03-30T19:09:58Z</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>heinrich.schuchardt@canonical.com</email>
</author>
<published>2023-03-03T22:31:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=fef0f1cc38a19f68e215fcc2504b4f60005179a2'/>
<id>urn:sha1:fef0f1cc38a19f68e215fcc2504b4f60005179a2</id>
<content type='text'>
Kconfig settings that are related to the API for standalone applications
should be in the API sub-menu and not on the top level.

CONFIG_STANDALONE_LOAD_ADDR is only relevant if standalone example
applications are built.

Signed-off-by: Heinrich Schuchardt &lt;heinrich.schuchardt@canonical.com&gt;
</content>
</entry>
<entry>
<title>Kconfig: Sort the BUILD_TARGET list</title>
<updated>2023-03-30T19:09:58Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut+renesas@mailbox.org</email>
</author>
<published>2023-02-28T06:22:21Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=66e49f047651f6e104d36db12e835b423d456108'/>
<id>urn:sha1:66e49f047651f6e104d36db12e835b423d456108</id>
<content type='text'>
Sort the defaults list in BUILD_TARGET Kconfig option. No functional change.

Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Move DISTRO_DEFAULTS into boot/</title>
<updated>2023-03-27T15:16:04Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2023-03-24T20:58:11Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c9d4abee6d88b6dd967f84d199a2fc41ef82b232'/>
<id>urn:sha1:c9d4abee6d88b6dd967f84d199a2fc41ef82b232</id>
<content type='text'>
This relates to booting so move it in to that Kconfig file, before
changing it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>powerpc/mpc85xx: Set default CONFIG_BUILD_TARGET</title>
<updated>2023-01-10T20:39:07Z</updated>
<author>
<name>Pali Rohár</name>
<email>pali@kernel.org</email>
</author>
<published>2022-12-29T01:39:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e0025d995788b8d5bdd079659a7d6cd60858442f'/>
<id>urn:sha1:e0025d995788b8d5bdd079659a7d6cd60858442f</id>
<content type='text'>
Final U-Boot binary for mpc85xx boards which use SPL and are not PBL-based
based is u-boot-with-spl.bin. PBL is not used only on boards with e500v1
and e500v2 cores. Apparently CONFIG_E500 is set not only for e500 cores,
but also for all other mpc85xx cores e500mc, e5500 and e5600. So do not use
CONFIG_E500 and instead filter new cores with PBL based bootrom.

Signed-off-by: Pali Rohár &lt;pali@kernel.org&gt;
</content>
</entry>
<entry>
<title>arm: mvebu: Fix default CONFIG_BUILD_TARGET</title>
<updated>2023-01-10T20:39:07Z</updated>
<author>
<name>Pali Rohár</name>
<email>pali@kernel.org</email>
</author>
<published>2022-12-29T01:39:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f0b1a1e13e17fe1f1d9d15e256cd89ac2c17c289'/>
<id>urn:sha1:f0b1a1e13e17fe1f1d9d15e256cd89ac2c17c289</id>
<content type='text'>
u-boot-with-spl.kwb is built only for SPL enabled 32-bit armada boards.
u-boot.kwb is built for 32-bit armada and kirkwood boards but only for
non-SPL targets.

So replace CONFIG_ARCH_MVEBU by CONFIG_ARMADA_32BIT (it implies
CONFIG_ARCH_MVEBU) for u-boot-with-spl.kwb.

And add additional CONFIG_ARMADA_32BIT &amp;&amp; !CONFIG_SPL for u-boot.kwb.

Signed-off-by: Pali Rohár &lt;pali@kernel.org&gt;
</content>
</entry>
</feed>
