<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/cmd, branch v2021.07-rc3</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/cmd?h=v2021.07-rc3</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/cmd?h=v2021.07-rc3'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2021-05-24T18:23:01Z</updated>
<entry>
<title>stackprot: Make our test a bit more complex</title>
<updated>2021-05-24T18:23:01Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2021-05-24T18:19:05Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2fc62f2991744dfeec65f8619092c359d8ecbcb0'/>
<id>urn:sha1:2fc62f2991744dfeec65f8619092c359d8ecbcb0</id>
<content type='text'>
With better compiler optimizations available, a compiler may see we do
nothing with our buffer after calling memset and omit the call, thus
causing us to not smash the stack.  Add a comment to explain why we now
also have a printf call, so that the test will pass as the memset will
not be omitted.

Reported-by: Marek Behún &lt;marek.behun@nic.cz&gt;
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>cmd: mvebu: Rename rx_training to mvebu_comphy_rx_training</title>
<updated>2021-05-16T04:48:45Z</updated>
<author>
<name>Stefan Roese</name>
<email>sr@denx.de</email>
</author>
<published>2021-05-05T07:15:10Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=961ab07df65efd54a062960081b22d769b7699b2'/>
<id>urn:sha1:961ab07df65efd54a062960081b22d769b7699b2</id>
<content type='text'>
Rename the misleading cmd "rx_training" to "mvebu_comphy_rx_training" to
avoid confusion and mixup with DDR3/4 training. This makes it clear,
that this command is platform specific and handles the COMPHY RX
training.

Also depend this cmd on ARMADA_8K and not TARGET_MVEBU_ARMADA_8K to make
is available for OcteonTX2 CN913x.

Signed-off-by: Stefan Roese &lt;sr@denx.de&gt;
Cc: Pali Rohár &lt;pali@kernel.org&gt;
Cc: Marek Behun &lt;marek.behun@nic.cz&gt;
Cc: Kostya Porotchkin &lt;kostap@marvell.com&gt;
Cc: Nadav Haklai &lt;nadavh@marvell.com&gt;
Acked-by: Marek Behún &lt;marek.behun@nic.cz&gt;
Acked-by: Pali Rohár &lt;pali@kernel.org&gt;
</content>
</entry>
<entry>
<title>cmd: add support for a new "extension" command</title>
<updated>2021-05-13T17:09:05Z</updated>
<author>
<name>Kory Maincent</name>
<email>kory.maincent@bootlin.com</email>
</author>
<published>2021-05-04T17:31:22Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=2f84e9cf06d31aa703ff31301bf811b3fcfc16cf'/>
<id>urn:sha1:2f84e9cf06d31aa703ff31301bf811b3fcfc16cf</id>
<content type='text'>
This patch adds a new "extension" command, which aims at detecting
extension boards connected to the hardware platform, and apply the
Device Tree overlays that describe the hardware present on those
extension boards.

In order to enable this mechanism, board-specific code must implement
the extension_board_scan() function that fills in a linked list of
"struct extension", each describing one extension board. In addition,
the board-specific code must select the SUPPORT_EXTENSION_SCAN Kconfig
boolean.

Based on this:

 - "extension scan" makes the generic code call the board-specific
   extension_board_scan() function to retrieve the list of detected
   extension boards.

 - "extension list" allows to list the detected extension boards.

 - "extension apply &lt;number&gt;|all" allows to apply the Device Tree
   overlay(s) corresponding to one, or all, extension boards

The latter requires two environment variables to exist and set one variable
to run:

 - extension_overlay_addr: the RAM address where to load the Device
   Tree overlays

 - extension_overlay_cmd: the U-Boot command to load one overlay.
   Indeed, the location and mechanism to load DT overlays is very setup
   specific.

 - extension_overlay_name: set by the command: the name of the DT which
   will be load during the execution.

When calling the command described in the extension_overlay_cmd
variable, the variable extension_overlay_name will be defined. So a
typical extension_overlay_cmd will look like this:

  extension_overlay_cmd=load mmc 0:1 $extension_overlay_addr /boot/$extension_overlay_name

Here is an example on how to use it:
=&gt; run loadfdt
=&gt; fdt addr $fdtaddr
=&gt; setenv extension_overlay_addr 0x1000
=&gt; setenv extension_overlay_cmd 'load mmc 0:1 ${extension_overlay_addr} /boot/${extension_overlay_name}'
=&gt; extension scan
Found 1 extension board(s).
=&gt; extension apply 0
519 bytes read in 3 ms (168.9 KiB/s)

Signed-off-by: Kory Maincent &lt;kory.maincent@bootlin.com&gt;
Reviewed-by: Maxime Ripard &lt;maxime@cerno.tech&gt;
</content>
</entry>
<entry>
<title>fdt_support: move fdt_valid from cmd_fdt.c to fdt_support.c</title>
<updated>2021-05-13T11:19:34Z</updated>
<author>
<name>Kory Maincent</name>
<email>kory.maincent@bootlin.com</email>
</author>
<published>2021-05-04T17:31:21Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=bbdbcaf59dc518f26897f162f3512a8a596c5d97'/>
<id>urn:sha1:bbdbcaf59dc518f26897f162f3512a8a596c5d97</id>
<content type='text'>
Move the fdt_valid function to fdt_support.
This changes allow to be able to test the validity of a devicetree in
other c files.

Update code syntax.

Signed-off-by: Kory Maincent &lt;kory.maincent@bootlin.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
Reviewed-by: Maxime Ripard &lt;maxime@cerno.tech&gt;
</content>
</entry>
<entry>
<title>x86: Correct regwidth prompt in cbsysinfo</title>
<updated>2021-05-10T05:56:12Z</updated>
<author>
<name>Simon Glass</name>
<email>sjg@chromium.org</email>
</author>
<published>2021-04-23T22:04:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=b8db1c138861b7d35d2206af6a555bab05a096a0'/>
<id>urn:sha1:b8db1c138861b7d35d2206af6a555bab05a096a0</id>
<content type='text'>
This should be 'regwidth', not 'baud'. Fix it.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
</content>
</entry>
<entry>
<title>Merge https://source.denx.de/u-boot/custodians/u-boot-riscv</title>
<updated>2021-05-07T12:57:32Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2021-05-07T12:57:32Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=07b53103b7a6c228ae8b74ae720b9c5d219ee7fd'/>
<id>urn:sha1:07b53103b7a6c228ae8b74ae720b9c5d219ee7fd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cmd/exception: support ebreak exception on RISC-V</title>
<updated>2021-05-05T08:13:12Z</updated>
<author>
<name>Heinrich Schuchardt</name>
<email>xypron.glpk@gmx.de</email>
</author>
<published>2021-04-09T10:48:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=91e4b7516d84cefab7324765b3c8d6a909185ce2'/>
<id>urn:sha1:91e4b7516d84cefab7324765b3c8d6a909185ce2</id>
<content type='text'>
The ebreak instruction should generate a breakpoint exception.

Signed-off-by: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Reviewed-by: Bin Meng &lt;bmeng.cn@gmail.com&gt;
Reviewed-by: Rick Chen &lt;rick@andestech.com&gt;
</content>
</entry>
<entry>
<title>cmd: gpt: Add option to write GPT partitions to environment variable</title>
<updated>2021-05-04T16:52:46Z</updated>
<author>
<name>Farhan Ali</name>
<email>farhan.ali@broadcom.com</email>
</author>
<published>2021-02-26T18:17:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=653cd92d66771cf1fbd1b7612b06a0874d316654'/>
<id>urn:sha1:653cd92d66771cf1fbd1b7612b06a0874d316654</id>
<content type='text'>
This change would enhance the existing 'gpt read' command to allow
(optionally) writing of the read GPT partitions to an environment
variable in the UBOOT partitions layout format. This would allow users
to easily change the overall partition settings by editing said variable
and then using the variable in the 'gpt write' and 'gpt verify' commands.

Signed-off-by: Farhan Ali &lt;farhan.ali@broadcom.com&gt;
Cc: Simon Glass &lt;sjg@chromium.org&gt;
Cc: Heinrich Schuchardt &lt;xypron.glpk@gmx.de&gt;
Cc: Corneliu Doban &lt;cdoban@broadcom.com&gt;
Cc: Rayagonda Kokatanur &lt;rayagonda.kokatanur@broadcom.com&gt;
Cc: Rasmus Villemoes &lt;rasmus.villemoes@prevas.dk&gt;
Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
</content>
</entry>
<entry>
<title>Merge tag 'xilinx-for-v2021.07-rc2' of https://source.denx.de/u-boot/custodians/u-boot-microblaze</title>
<updated>2021-04-29T15:31:06Z</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2021-04-29T15:31:06Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f3a0d2c1af630cc09a34c2159aa2dfa12b831762'/>
<id>urn:sha1:f3a0d2c1af630cc09a34c2159aa2dfa12b831762</id>
<content type='text'>
Xilinx changes for v2021.07-rc2

xilinx:
- Enable saving variables based on bootmode
- Cleanup usb dfu setup and wire it up with usb bootmode
- Fix bootscript address logic
- Remove GD references (spi, Versal)
- Enable capsule update

clk:
- Small Kconfig fix

net:
- Fix gmii2rgmii bridge binding

usb:
- Propagate error (dfu gadget)
</content>
</entry>
<entry>
<title>phy: marvell: add RX training command</title>
<updated>2021-04-29T05:45:24Z</updated>
<author>
<name>Igal Liberman</name>
<email>igall@marvell.com</email>
</author>
<published>2021-03-23T10:57:57Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e49cdbe10b082980029b8e215842be4fbbd13f5f'/>
<id>urn:sha1:e49cdbe10b082980029b8e215842be4fbbd13f5f</id>
<content type='text'>
This patch adds support for running RX training using new command called
"rx_training"
Usage:
rx_training - rx_training &lt;cp id&gt; &lt;comphy id&gt;

RX training allows to improve link quality (for SFI mode)
by running training sequence between us and the link partner,
this allows to reach better link quality then using static configuration.

Change-Id: I818fe67ccaf19a87af50d4c34a9db7d6802049a5
Signed-off-by: Igal Liberman &lt;igall@marvell.com&gt;
Signed-off-by: Marcin Wojtas &lt;mw@semihalf.com&gt;
</content>
</entry>
</feed>
