upstream u-boot with additional patches for our devices/boards: https://lists.denx.de/pipermail/u-boot/2017-March/282789.html (AXP crashes) ; Gbit ethernet patch for some LIME2 revisions ; with SPI flash support

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Simon Glass e48eeb9ea3 dm: blk: Improve block device claiming ... The intention with block devices is that the device number (devnum field in its descriptor) matches the alias of its parent device. For example, with: aliases { mmc0 = "/sdhci@700b0600"; mmc1 = "/sdhci@700b0400"; } we expect that the block devices for mmc0 and mmc1 would have device numbers of 0 and 1 respectively. Unfortunately this does not currently always happen. If there is another MMC device earlier in the driver model data structures its block device will be created first. It will therefore get device number 0 and mmc0 will therefore miss out. In this case the MMC device will have sequence number 0 but its block device will not. To avoid this, allow a device to request a device number and bump any existing device number that is using it. This all happens during the binding phase so it is safe to change these numbers around. This allows device numbers to match the aliases in all circumstances. Add a test to verify the behaviour. Signed-off-by: Simon Glass <sjg@chromium.org>		8 years ago
..
arc	…
arm	dm: core: Replace of_offset with accessor (part 2)	8 years ago
avr32	…
m68k	…
microblaze	…
mips	mips: bmips: fix BCM3380 periph clock frequency	8 years ago
nds32	…
nios2	…
powerpc	…
sandbox	dm: blk: Improve block device claiming	8 years ago
sh	…
x86	…
xtensa	…
.gitignore	…
Kconfig	Kconfig: Finish migration of hashing commands	8 years ago