<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/board/nvidia, branch master</title>
<subtitle>Broadcom-s U-Boot</subtitle>
<id>https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/project/bcm63xx/u-boot/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/'/>
<updated>2019-06-05T16:16:35Z</updated>
<entry>
<title>p2771-0000: Add support for framebuffer carveouts</title>
<updated>2019-06-05T16:16:35Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-04-15T09:32:36Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=c79aa81dbc8a753ac8b00adbfb8c355933b89caa'/>
<id>urn:sha1:c79aa81dbc8a753ac8b00adbfb8c355933b89caa</id>
<content type='text'>
If early firmware initialized the display hardware and the display
controllers are scanning out a framebuffer (e.g. a splash screen), make
sure to pass information about the memory location of that framebuffer
to the kernel before booting to avoid the kernel from using that memory
for the buddy allocator.

This same mechanism can also be used in the kernel to set up early SMMU
mappings and avoid SMMU faults caused by the display controller reading
from memory for which it has no mapping.

Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>p2371-2180: Add support for framebuffer carveouts</title>
<updated>2019-06-05T16:16:35Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-04-15T09:32:35Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=595ea7381bc30839bf6f01ccdf1236020ad1958f'/>
<id>urn:sha1:595ea7381bc30839bf6f01ccdf1236020ad1958f</id>
<content type='text'>
If early firmware initialized the display hardware and the display
controllers are scanning out a framebuffer (e.g. a splash screen), make
sure to pass information about the memory location of that framebuffer
to the kernel before booting to avoid the kernel from using that memory
for the buddy allocator.

This same mechanism can also be used in the kernel to set up early SMMU
mappings and avoid SMMU faults caused by the display controller reading
from memory for which it has no mapping.

Reviewed-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>p2771-0000: Pass Ethernet MAC to the kernel</title>
<updated>2019-06-05T16:16:35Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-04-15T09:32:34Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=8317189737a93753f634e0f14d984226b7a2da4c'/>
<id>urn:sha1:8317189737a93753f634e0f14d984226b7a2da4c</id>
<content type='text'>
Pass the ethernet MAC address to the kernel upon boot. This passes both
the local-mac-address property (as passed to U-Boot from cboot) and the
currently set MAC address via the mac-address property. The latter will
only be set if it is different from the address that was already passed
via the local-mac-address property.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>p2371-2180: Pass Ethernet MAC to the kernel</title>
<updated>2019-06-05T16:16:35Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-04-15T09:32:33Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=a930a727423c6559ccf0b35c833669ad491a3db5'/>
<id>urn:sha1:a930a727423c6559ccf0b35c833669ad491a3db5</id>
<content type='text'>
Pass the ethernet MAC address to the kernel upon boot. This passes both
the local-mac-address property (as passed to U-Boot from cboot) and the
currently set MAC address via the mac-address property. The latter will
only be set if it is different from the address that was already passed
via the local-mac-address property.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>ARM: tegra: Unify Tegra186 builds</title>
<updated>2019-06-05T16:16:34Z</updated>
<author>
<name>Thierry Reding</name>
</author>
<published>2019-04-15T09:32:28Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=a0dbc1314c3275c3af3591fc6f4762ff3367a4fd'/>
<id>urn:sha1:a0dbc1314c3275c3af3591fc6f4762ff3367a4fd</id>
<content type='text'>
Tegra186 build are currently dealt with in very special ways, which is
because Tegra186 is fundamentally different in many respects. It is no
longer necessary to do many of the low-level programming because early
boot firmware will already have taken care of it.

Unfortunately, separating Tegra186 builds from the rest in this way
makes it difficult to share code with prior generations of Tegra. With
all of the low-level programming code behind Kconfig guards, the build
for Tegra186 can again be unified.

As a side-effect, and partial reason for this change, other Tegra SoC
generations can now make use of the code that deals with taking over a
boot from earlier bootloaders. This used to be nvtboot, but has been
replaced by cboot nowadays. Rename the files and functions related to
this to avoid confusion. The implemented protocols are unchanged.

Signed-off-by: Thierry Reding &lt;treding@nvidia.com&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>tegra: nyan: Add a README</title>
<updated>2019-05-24T17:14:15Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-04-01T20:38:42Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=593216f9cb16978e5178c15bd51b82327d6270f3'/>
<id>urn:sha1:593216f9cb16978e5178c15bd51b82327d6270f3</id>
<content type='text'>
Add a short note about how to boot U-Boot on Nyan-big using tegrarcm.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>tegra: Correct tegra124 clock name</title>
<updated>2019-05-24T17:13:12Z</updated>
<author>
<name>Simon Glass</name>
</author>
<published>2019-04-01T20:38:38Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=f6ac3fab9ba2aa4b352fd8c8799c4b5091fc376c'/>
<id>urn:sha1:f6ac3fab9ba2aa4b352fd8c8799c4b5091fc376c</id>
<content type='text'>
The first clock type appears to have and incorrect setting for out of the
mux outputs. It should be CLK_M, not OSC. Fix it and its only user.

Signed-off-by: Simon Glass &lt;sjg@chromium.org&gt;
Signed-off-by: Tom Warren &lt;twarren@nvidia.com&gt;
</content>
</entry>
<entry>
<title>SPDX: Convert all of our single license tags to Linux Kernel style</title>
<updated>2018-05-07T13:34:12Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-05-06T21:58:06Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=83d290c56fab2d38cd1ab4c4cc7099559c1d5046'/>
<id>urn:sha1:83d290c56fab2d38cd1ab4c4cc7099559c1d5046</id>
<content type='text'>
When U-Boot started using SPDX tags we were among the early adopters and
there weren't a lot of other examples to borrow from.  So we picked the
area of the file that usually had a full license text and replaced it
with an appropriate SPDX-License-Identifier: entry.  Since then, the
Linux Kernel has adopted SPDX tags and they place it as the very first
line in a file (except where shebangs are used, then it's second line)
and with slightly different comment styles than us.

In part due to community overlap, in part due to better tag visibility
and in part for other minor reasons, switch over to that style.

This commit changes all instances where we have a single declared
license in the tag as both the before and after are identical in tag
contents.  There's also a few places where I found we did not have a tag
and have introduced one.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Remove unnecessary instances of DECLARE_GLOBAL_DATA_PTR</title>
<updated>2018-04-27T18:54:48Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2018-04-18T17:50:47Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=d024236e5a31a2b4b82cbcc98b31b8170fc88d28'/>
<id>urn:sha1:d024236e5a31a2b4b82cbcc98b31b8170fc88d28</id>
<content type='text'>
We have a large number of places where while we historically referenced
gd in the code we no longer do, as well as cases where the code added
that line "just in case" during development and never dropped it.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>MAINTAINERS: Add missing boards and config entries</title>
<updated>2017-11-06T14:58:51Z</updated>
<author>
<name>Tom Rini</name>
</author>
<published>2017-10-21T16:54:02Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/project/bcm63xx/u-boot/commit/?id=79df00fdb40b4584919c8bcef42d323a8d38d0f1'/>
<id>urn:sha1:79df00fdb40b4584919c8bcef42d323a8d38d0f1</id>
<content type='text'>
As part of my usual round of build testing, output about missing
MAINTAINERS information was not logged, and thus often overlooked.
Correct that mistake by ensuring that I log the output of
genboardscfg.py every time.  As part of that, address a number of
missing MAINTAINERS entires.  In the case of a missing file, I have put
the original submitter down.  In the rest of the cases I have added the
config (and sometimes relevant header file) to the existing set of file
globs.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
