<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/cmd/Kconfig, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-06-13T07:21:06Z</updated>
<entry>
<title>Kconfig: Add SPI / SPI_FLASH as dependencies</title>
<updated>2019-06-13T07:21:06Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2019-05-29T21:01:28Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=a4298ddaf8bbccf8a14acb6be33764eecbea9abd'/>
<id>urn:sha1:a4298ddaf8bbccf8a14acb6be33764eecbea9abd</id>
<content type='text'>
In order to use CMD_SF / CMD_SPI / ENV_IS_IN_SPI_FLASH we need to have
the SPI (or SPI_FLASH/DM_SPI_FLASH, for CMD_SF) enabled.  Express this
in the Kconfigs.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Jagan Teki &lt;jagan@amarulasolutions.com&gt;
</content>
</entry>
<entry>
<title>cmd: remove unused `display` command</title>
<updated>2019-05-28T22:55:08Z</updated>
<author>
<name>Heinrich Schuchardt</name>
</author>
<published>2019-05-21T05:49:58Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=005a804d0f3a0f0ace28a097142401ef9778e74c'/>
<id>urn:sha1:005a804d0f3a0f0ace28a097142401ef9778e74c</id>
<content type='text'>
Compiling the display command leads to an error

    undefined reference to `display_set'

No implementation of display_set() exists in U-Boot.

Eliminate the `display` command as well as the accompanying files.

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>efi_loader: make device path to text protocol customizable</title>
<updated>2019-05-12T18:54:22Z</updated>
<author>
<name>Heinrich Schuchardt</name>
</author>
<published>2019-05-11T07:53:33Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=64b5ba4d293ac9b5416c286aa2d0051b6a9594d6'/>
<id>urn:sha1:64b5ba4d293ac9b5416c286aa2d0051b6a9594d6</id>
<content type='text'>
The device path to text protocol is not needed for EBBR compliance. So
let's make it a customizable option.

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
</content>
</entry>
<entry>
<title>cmd: ubifs: Remove select for non-existent option</title>
<updated>2019-05-10T11:18:13Z</updated>
<author>
<name>Chris Packham</name>
</author>
<published>2019-04-13T09:13:56Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=2b841dba5ccea242fce12d5a3142042138c5a23a'/>
<id>urn:sha1:2b841dba5ccea242fce12d5a3142042138c5a23a</id>
<content type='text'>
There is no 'config CRC32', remove the select that was attempting to use
it.

Reported-by: Robert P. J. Day &lt;rpjday@crashcourse.ca&gt;
Signed-off-by: Chris Packham &lt;judge.packham@gmail.com&gt;
Reviewed-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>RISCV: image: Add booti support</title>
<updated>2019-05-09T08:47:52Z</updated>
<author>
<name>Atish Patra</name>
</author>
<published>2019-05-07T00:49:39Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=3cedc97479ff44cdc00485de7517a833e3dfb630'/>
<id>urn:sha1:3cedc97479ff44cdc00485de7517a833e3dfb630</id>
<content type='text'>
This patch adds booti support for RISC-V Linux kernel. The existing
bootm method will also continue to work as it is.

It depends on the following kernel patch which adds the header to the
flat Image. Gzip compressed Image (Image.gz) support is not enabled with
this patch.

https://patchwork.kernel.org/patch/10925543/

Tested on HiFive Unleashed and QEMU.

Signed-off-by: Atish Patra &lt;atish.patra@wdc.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Tested-by: Karsten Merker &lt;merker@debian.org&gt;
Reviewed-by: Marek Vasut &lt;marek.vasut@gmail.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of git://git.denx.de/u-boot-socfpga</title>
<updated>2019-04-26T17:49:58Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2019-04-26T17:49:58Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=1c64692df20c1f491ea79de3a732428611bb0ba0'/>
<id>urn:sha1:1c64692df20c1f491ea79de3a732428611bb0ba0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Revert "cmd: Kconfig: Do not include EEPROM if DM_I2C is used without DM_I2C_COMPAT"</title>
<updated>2019-04-24T22:00:49Z</updated>
<author>
<name>Simon Goldschmidt</name>
</author>
<published>2019-03-26T12:38:53Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=bbecfd4cf2a8f7baeef6037303b8b4380a71aa12'/>
<id>urn:sha1:bbecfd4cf2a8f7baeef6037303b8b4380a71aa12</id>
<content type='text'>
This reverts commit 65a97e7fcf54feb7c4ebe1aee8a572830af4cf51.

The 'eeprom' command has been converted to work with DM_I2C in a patch
submitted around the same time as this commit:
commit 0c07a9b4078d ("eeprom: Add device model based I2C support to eeprom command")

Signed-off-by: Simon Goldschmidt &lt;simon.k.r.goldschmidt@gmail.com&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>Merge tag 'pull-24apr19' of git://git.denx.de/u-boot-dm</title>
<updated>2019-04-24T16:27:29Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2019-04-24T16:27:29Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=7d994067424776b6184872b82fcaf4c0b95528f9'/>
<id>urn:sha1:7d994067424776b6184872b82fcaf4c0b95528f9</id>
<content type='text'>
Various minor sandbox iumprovements
Fixes for tracing with sandbox
Refactoring for boot_get_fdt()
</content>
</entry>
<entry>
<title>Convert CONFIG_TRACE to Kconfig</title>
<updated>2019-04-24T02:26:43Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-04-08T19:20:51Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=a24a78d7e3e8b6008423d1a6aa49a6c9eb904752'/>
<id>urn:sha1:a24a78d7e3e8b6008423d1a6aa49a6c9eb904752</id>
<content type='text'>
This converts the following to Kconfig:
   CONFIG_TRACE

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>common: command: Add command execution tracer.</title>
<updated>2019-04-24T02:26:43Z</updated>
<author>
<name>Christoph Muellner</name>
</author>
<published>2019-04-05T11:03:46Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=7ae31fccec16d4885f1704b089eb018be836f619'/>
<id>urn:sha1:7ae31fccec16d4885f1704b089eb018be836f619</id>
<content type='text'>
When using boot scripts it can become quite hard to understand
which commands are actually executed during bootup (e.g. where
is a kernel image loaded from or which DTB is in use).

Shell scripts suffer from a similar problem and many shells address
this problem with a command execution tracer (e.g. BASH has xtrace,
which can be enabled by "set -x").

This patch introduces a command tracer for U-Boot, which prints
every command with its arguments before it is executed.

Signed-off-by: Christoph Muellner &lt;christoph.muellner@theobroma-systems.com&gt;
Reviewed-by: Philipp Tomsich &lt;philipp.tomsich@theobroma-systems.com&gt;
</content>
</entry>
</feed>
