<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bcm63xx/u-boot/board/keymile/scripts/develop-common.txt, 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>2015-11-18T20:28:51Z</updated>
<entry>
<title>km/scripts: search for kernel/DTBs at serverip:/PRODUCTNAME via TFTP in develop mode</title>
<updated>2015-11-18T20:28:51Z</updated>
<author>
<name>Tobias Müller</name>
</author>
<published>2015-11-13T15:15:22Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=ef3f2f08f7fb0d3526ce1b78a22b41afce75e6aa'/>
<id>urn:sha1:ef3f2f08f7fb0d3526ce1b78a22b41afce75e6aa</id>
<content type='text'>
Search for the kernel and DTBs in a folder named PRODUCTNAME (found in the IVM)
at the TFTP server instead of the u-boot boardname.

Signed-off-by: Tobias Müller &lt;Tobias.Mueller@keymile.com&gt;
Signed-off-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
Reviewed-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>km/scripts: load fdt_bid_kwkey.dtb when working with tftp</title>
<updated>2015-11-18T20:28:50Z</updated>
<author>
<name>Holger Brunck</name>
</author>
<published>2015-11-13T15:15:21Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=91b9db0be55d36948104e8fd4ef12ca3ef182b0e'/>
<id>urn:sha1:91b9db0be55d36948104e8fd4ef12ca3ef182b0e</id>
<content type='text'>
When loading the dtb file via tftp we should load the one which matches
boardId and hwKey and not a common one for the boardname. We have boards
were different hwKeys are used and then we may load an incorrect dtb
file. If no fdt_bid_kwkey.dtb file is not a fallback to boardname.dtb is used.

Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
Signed-off-by: Tobias Müller &lt;Tobias.Mueller@keymile.com&gt;
Signed-off-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
Reviewed-by: Heiko Schocher &lt;hs@denx.de&gt;
</content>
</entry>
<entry>
<title>arm/km: define fdt_high env variable and allow backwards compatibility</title>
<updated>2014-02-13T15:18:13Z</updated>
<author>
<name>Gerlando Falauto</name>
</author>
<published>2014-01-27T15:58:28Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=b1c2a7ae32b6c5dd1dcb7cb29c862af01523ba36'/>
<id>urn:sha1:b1c2a7ae32b6c5dd1dcb7cb29c862af01523ba36</id>
<content type='text'>
Add set_fdthigh subcommand to "subbootcmds" (release) so to set "fdt_high"
This is necessary on Kirkwood so that the FDT does not get relocated
above the memory limit that the kernel cannot access
(that is the memory part reserved for the switch).
This was tested on NUSA1, where it is necessary, and on ETER1, where it
doesn't seem to hurt.

We want the scripts to also work with older versions of u-boot, where:
a) set_fdthigh is not defined (will be default env for newer u-boots)
b) the fdt will not be available

For this reason, we use "set_fdthigh" to tell whether we are running
a newer (FDT-aware) u-boot or not.
So if "set_fdthigh" runs successfully or arch != arm we try loading
the fdt; otherwise we proceed normally.

Notice how, contrary to release mode, set_fdthigh will _not_ be part of
subbootcmds for develop and ramfs, but will be executed as part of
"tftpfdt".

Since this is only needed for kirkwood cards, and it prevents the kernel
from booting on QorIQ (though it seemed to work on ETER1), we change
its definition in the default env for powerpc so that the value is only
set on ARM.

Signed-off-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
Signed-off-by: Gerlando Falauto &lt;gerlando.falauto@keymile.com&gt;
Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
Acked-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
</content>
</entry>
<entry>
<title>arm/km: enable FDT for km_kirwkood</title>
<updated>2014-02-13T15:17:54Z</updated>
<author>
<name>Gerlando Falauto</name>
</author>
<published>2014-01-27T15:58:27Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=7b2268b88fb9a67b13563fa61b8ae282b9aa6e00'/>
<id>urn:sha1:7b2268b88fb9a67b13563fa61b8ae282b9aa6e00</id>
<content type='text'>
This consists of:
a) Defining the addresses, enabling fdtsupport [arm]
b) Defining "cramfsloadfdt"  [arm,powerpc =&gt; common]
c) Adding the FDT address to bootm [arm,powerpc =&gt; common]
d) Defining "tftpfdt" in ramfs-,develop- [arm,powerpc &gt;= common]

This should work with 3.10 kernels, whether loaded through TFTP
(with rootfs either through NFS or TFTP-ramfs) or from the NAND.

The machid was left unchanged, this should keep compatibility with both
older and newer kernels.

Signed-off-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
Signed-off-by: Gerlando Falauto &lt;gerlando.falauto@keymile.com&gt;
Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
Acked-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
</content>
</entry>
<entry>
<title>km/scripts: replace hardcoded uImage</title>
<updated>2013-02-15T23:47:20Z</updated>
<author>
<name>Andreas Huber</name>
</author>
<published>2013-01-21T03:55:21Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=d42a3b74980e65e72185a07f9f556e00587e7349'/>
<id>urn:sha1:d42a3b74980e65e72185a07f9f556e00587e7349</id>
<content type='text'>
Replace uImage with ${uimage}.
If uimage is not set, default it to uImage.

Signed-off-by: Andreas Huber &lt;andreas.huber@keymile.com&gt;
Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
</content>
</entry>
<entry>
<title>km/common: add toolchain variable</title>
<updated>2011-12-20T22:43:45Z</updated>
<author>
<name>Holger Brunck</name>
</author>
<published>2011-12-14T06:11:50Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=d26982cbb6c663dff5d5a956068f4ec384cfc2ba'/>
<id>urn:sha1:d26982cbb6c663dff5d5a956068f4ec384cfc2ba</id>
<content type='text'>
Add a variable "toolchain" and configure the rootpath
for the nfsargs with this variable.

Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
cc: Wolfgang Denk &lt;wd@denx.de&gt;
</content>
</entry>
<entry>
<title>km/common: fix ramfs development target</title>
<updated>2011-10-21T22:29:09Z</updated>
<author>
<name>Andreas Huber</name>
</author>
<published>2011-09-13T23:06:11Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=2a7714ce64cfd954535f0c96f2809e2fd80d84f0'/>
<id>urn:sha1:2a7714ce64cfd954535f0c96f2809e2fd80d84f0</id>
<content type='text'>
Calucations of PRAM needs to take into account the 'rootfssize'.
Memory available to the linux kernel 'mem=' is in all cases set to the total
memory size minus the pram size.

Signed-off-by: Andreas Huber &lt;andreas.huber@keymile.com&gt;
Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
cc: Wolfgang Denk &lt;wd@denx.de&gt;
</content>
</entry>
<entry>
<title>km/common: simplify debug environment</title>
<updated>2011-07-27T21:43:33Z</updated>
<author>
<name>Holger Brunck</name>
</author>
<published>2011-07-04T21:52:52Z</published>
<link rel='alternate' type='text/html' href='https://git-03.infra.openwrt.org/project/bcm63xx/u-boot/commit/?id=b648bfc212c0e62dae47b8f09a0c4e49bbd89106'/>
<id>urn:sha1:b648bfc212c0e62dae47b8f09a0c4e49bbd89106</id>
<content type='text'>
The debug environment which is stored in textfiles in the
scripts directory was reworked. Two usecase are now present
which can be executed simply from the default environment:
run develop: this configures the environment to setup the
             rootfs via nfs
run ramfs: this configures the environment to setup the
           rootfs in ram

Each architecture now has a "arch" variable which is used
to load the architecture specific debug scripts and to set
the rootpath for NFS.

Signed-off-by: Holger Brunck &lt;holger.brunck@keymile.com&gt;
Signed-off-by: Valentin Longchamp &lt;valentin.longchamp@keymile.com&gt;
cc: Heiko Schocher &lt;hs@denx.de&gt;
cc: Wolfgang Denk &lt;wd@denx.de&gt;
</content>
</entry>
</feed>
