u-boot.git/README, branch v2014.10-rc2

cmd_bootm.c: Add 'booti' for ARM64 Linux kernel Images

2014-08-30T11:46:41Z

The default format for arm64 Linux kernels is the "Image" format, described in Documentation/arm64/booting.txt. This, along with an optional gzip compression on top is all that is generated by default. The Image format has a magic number within the header for verification, a text_offset where the Image must be run from, an image_size that includes the BSS and reserved fields. This does not support automatic detection of a gzip compressed image. Signed-off-by: Tom Rini

Merge branch 'master' of git://www.denx.de/git/u-boot-imx

2014-08-29T15:06:51Z

mtd, ubi, ubifs: resync with Linux-3.14

2014-08-25T23:25:55Z

resync ubi subsystem with linux: commit 455c6fdbd219161bd09b1165f11699d6d73de11c Author: Linus Torvalds Date: Sun Mar 30 20:40:15 2014 -0700 Linux 3.14 A nice side effect of this, is we introduce UBI Fastmap support to U-Boot. Signed-off-by: Heiko Schocher Signed-off-by: Tom Rini Cc: Marek Vasut Cc: Sergey Lapin Cc: Scott Wood Cc: Joerg Krause

Merge branch 'agust@denx.de' of git://git.denx.de/u-boot-staging

2014-08-25T12:34:39Z

net: More BOOTP retry timeout improvements

2014-08-21T16:01:30Z

It's not unusual for DHCP servers to take a couple hundred milliseconds to respond to DHCP discover messages. One possible reason for the delay can be that the server checks (typically using an ARP request) that the IP it's about to hand out isn't in use yet. To make matters worse, some servers may also queue up requests and process them sequentially, which can cause excessively long delays if clients retry too fast. Commit f59be6e850b3 ("net: BOOTP retry timeout improvements") shortened the retry timeouts significantly, but the BOOTP/DHCP implementation in U-Boot doesn't handle that well because it will ignore incoming replies to earlier requests. In one particular setup this increases the time it takes to obtain a DHCP lease from 630 ms to 8313 ms. This commit attempts to fix this in two ways. First it increases the initial retry timeout from 10 ms to 250 ms to give DHCP servers some more time to respond. At the same time a cache of outstanding DHCP request IDs is kept so that the implementation will know to continue transactions even after a retransmission of the DISCOVER message. The maximum retry timeout is also increased from 1 second to 2 seconds. An ID cache of size 4 will keep DHCP requests around for 8 seconds (once the maximum retry timeout has been reached) before dropping them. This should give servers plenty of time to respond. If it ever turns out that this isn't enough, the size of the cache can easily be increased. With this commit the DHCP lease on the above-mentioned setup still takes longer (1230 ms) than originally, but that's an acceptable compromise to improve DHCP lease acquisition time for a broader range of setups. To make it easier to benchmark DHCP in the future, this commit also adds the time it took to obtain a lease to the final "DHCP client bound to address x.x.x.x" message. Tested-by: Stephen Warren Signed-off-by: Thierry Reding

README: document CONFIG_BOARD_SIZE_LIMIT

2014-08-14T13:57:08Z

CONFIG_BOARD_SIZE_LIMIT was introduced by f3a14d37 [Makefile: allow boards to check file size limits] and is in use by several boards, but never got documented. Signed-off-by: Sascha Silbe

RTC: add support for DS1339 (using DS1307 driver)

2014-08-14T12:45:58Z

Signed-off-by: Markus Niebel

Merge branch 'master' of git://git.denx.de/u-boot-arm

2014-08-11T08:21:03Z

Conflicts: boards.cfg Signed-off-by: Stefano Babic

Merge branch 'master' of git://git.denx.de/u-boot-arm

2014-08-08T08:18:40Z

The _config target is not present anymore, mention _defconfig instead

2014-08-06T13:02:46Z

The _config part is gone for sure, the _defconfig target could at least work. I have not verified this for all targets though.