{"push_id":1048087390,"size":8,"distinct_size":8,"ref":"refs/heads/rpi_dev","head":"41e176d4d893a720f97a1387e6e3a25aae679d5f","before":"68debfab835f60cac34e5e14ab736e20e98b96c3","commits":[{"sha":"82053d742db38b54bdd2bfb8d84c4d08ce778716","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"APPLIED: smsc95xx: fix operation on 64-bit systems\n\nsmsc95xx_read_reg() should calculate sizeof(*data) not sizeof(data) since\ndata is a pointer, and the value pointed at is being transferred over USB,\nnot the value of the pointer. This fixes operation of the driver in 64-bit\nbuilds, such as the Raspberry Pi 3.\n\nReported-by: Eric Anholt <eric@anholt.net>\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nAcked-by: Marek Vasut <marex@denx.de>\nAcked-by: Joe Hershberger <joe.hershberger@ni.com>","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/82053d742db38b54bdd2bfb8d84c4d08ce778716"},{"sha":"e77a5ae10325d39093c640ccb6d7c98a059b0c8c","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"APPLIED: ARM: bcm2835: move CONFIG_BCM283* to Kconfig\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\n---\nv2: No change.\n\nThis series depends on:\n\n* My series beginning with \"ARM: bcm283x: don't always define\n  CONFIG_BCM2835\"\n* My patch \"serial: add BCM283x mini UART driver\".\n* Alexander Graf's arm64 page table/cache series starting with\n  \"arm64: Add 32bit arm compatible dcache definitions\".","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/e77a5ae10325d39093c640ccb6d7c98a059b0c8c"},{"sha":"451c731972f635a282bdbd4f422b144cd5aed796","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"APPLIED: rpi: use constant \"unknown board\" DT filename\n\nTo simplify support for new SoCs, just use a constant filename\nfor the unknown case. In practice this case shouldn't be hit anyway, so\nthe filename isn't relevant, and certainly doesn't need to differentiate\nbetween SoCs. If a user has an as-yet-unknown board, they can override\nthis value in the environment anyway.\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\n---\nv2: No change.","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/451c731972f635a282bdbd4f422b144cd5aed796"},{"sha":"06876c5ee8142e34d42608b0255f87706bb8d64f","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"APPLIED: rpi: add Raspberry Pi 3 board ID\n\nThis allows U-Boot to known the name of the board.\n\nThe existing rpi_2_defconfig can operate correctly on the Raspberry Pi 3\nin 32-bit mode /if/ you have configured the firmware to use the PL011 UART\nas the console UART (the default is the mini UART). This requires two\nthings:\na) config.txt should contain dtoverlay=pi3-miniuart-bt\nb) You should run the following to tell the VC FW to process DT when\nbooting, and copy u-boot.bin.img (rather than u-boot.bin) to the SD card\nas the kernel image:\n\n   path/to/kernel/scripts/mkknlimg --dtok u-boot.bin u-boot.bin.img\n\nThis works as of firmware.git commit 046effa13ebc \"firmware: arm_loader:\nemmc clock depends on core clock See:\nhttps://github.com/raspberrypi/firmware/issues/572\".\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\n---\nv2: Enhance the commit description to contain complete details re: how to\nrun rpi_2_defconfig on a Raspberry Pi 3.","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/06876c5ee8142e34d42608b0255f87706bb8d64f"},{"sha":"15a2894d1904e11d7516ecde7ce4e1c063d8c16e","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"APPLIED: ARM: bcm2835: expand Kconfig target descriptions\n\nThis adds an explanation of which Raspberry Pi models each target option\nsupports.\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\n---\nv2: Enhance the Kconfig description to contain complete details re: how to\nrun rpi_2_defconfig on a Raspberry Pi 3.","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/15a2894d1904e11d7516ecde7ce4e1c063d8c16e"},{"sha":"5592d1ebfc6846fdb0e8586dfa9639ab2863282c","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"APPLIED: rpi: BCM2837 and Raspberry Pi 3 32-bit support\n\nThe Raspberry Pi 3 contains a BCM2837 SoC. The BCM2837 is a BCM2836 with\nthe CPU complex swapped out for a quad-core ARMv8. This can operate in 32-\nor 64-bit mode. 32-bit mode is the current default selected by the\nVideoCore firmware on the Raspberry Pi 3. This patch adds a 32-bit port of\nU-Boot for the Raspberry Pi 3.\n\nFrom U-Boot's perspective, the only delta between the RPi 2 and RPi 3 is a\nchange in usage of the SoC UARTs. On all previous Pis, the PL011 was the\nonly UART in use. The Raspberry Pi 3 adds a Bluetooth module which uses a\nUART to connect to the SoC. By default, the PL011 is used for this purpose\nsince it has larger FIFOs than the other \"mini\" UART. However, this can\nbe configured via the VideoCore firmware's config.txt file. This patch\nhard-codes use of the mini UART in the RPi 3 port. If your system uses the\nPL011 UART for the console even on the RPi 3, please use the RPi 2 U-Boot\nport instead. A future change might determine which UART to use at\nrun-time, thus allowing the RPi 2 and RPi 3 (32-bit) ports to be squashed\ntogether.\n\nThe mini UART has some limitations. One externally visible issue in the\nBCM2837 integration is that the UART divides the SoC's \"core clock\" to\ngenerate the baud rate. The core clock is typically variable, and under\ncontrol of the VideoCore firmware for thermal management reasons. If the\nVC FW does modify the core clock rate, UART communication will be\ncorrupted since the baud rate will vary from the expected value. This was\nnot an issue for the PL011 UART, since it is fed by a fixed 3MHz clock. To\nwork around this, the VideoCore firmware can be told not to modify the SoC\ncore clock. However, the only way this can happen and be thermally safe is\nto limit the core clock to a low/minimum frequency. This leaves\nperformance on the table for use-cases that don't care about a UART\nconsole. Consequently, use of the mini UART console must be explicitly\nrequested by entering the following line into config.txt:\n\n    enable_uart=1\n\nA recent version of the VC firmware is required to ensure that the mini\nUART is fully and correctly initialized by the VC FW; at least\nfirmware.git 046effa13ebc \"firmware: arm_loader: emmc clock depends on\ncore clock See: https://github.com/raspberrypi/firmware/issues/572\".\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\n---\nv2:\n- Fix Kconfig syntax error.\n- Update required VC FW commit ID to cover MMC fix too.","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/5592d1ebfc6846fdb0e8586dfa9639ab2863282c"},{"sha":"87941c30cf7c2328030ab742b57007e664f0cdb9","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"ARM: allow CONFIG_GICV* not to be defined\n\nThere are ARM SoCs (such as the BCM2837) do not contain an ARM GIC. Fix\nthe ARMv8 CPU startup code to compile in this case.\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/87941c30cf7c2328030ab742b57007e664f0cdb9"},{"sha":"41e176d4d893a720f97a1387e6e3a25aae679d5f","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"ARM: add Raspberry Pi 3 64-bit config\n\nOn all Pis so far, the VC FW provides a short stub to set up the ARM CPU\nbefore entering the kernel (a/k/a U-Boot for us). This feature is not\ncurrently supported by the VC FW when booting in 64-bit mode. However,\nthis feature will likely appear in the near future, and this U-Boot port\nassumes that such a feature is in place. Without that feature, or a\ntemporary workaround described below, U-Boot will not boot.\n\nOnce the VC FW does provide the ARM stub, u-boot.bin built for rpi_3 can\nbe used drectly as kernel7.img, in the same way as any other RPi port. The\nfollowing config.txt is required:\n\n    # Fix mini UART input frequency, and setup/enable up the UART.\n    # Without this option, U-Boot will not boot, even if you don't care\n    # about the serial console. This option will always be required for\n    # all RPi3 use-cases, unless the PL011 UART is used, which is not\n    # yet supported by rpi_3* builds of U-Boot.\n    enable_uart=1\n    # Boot in AArch64 (64-bit) mode.\n    # It is possible that a future VC FW will remove the need for this\n    # option, instead auto-setting 32-/64-bit mode based on the \"kernel\"\n    # filename present on the SD card.\n    arm_control=0x200\n\nPrior to the VC FW providing the ARM boot stub, you can use the following\nsteps to build an equivalent stub into the U-Boot binary:\n\ngit clone https://github.com/swarren/rpi-3-aarch64-demo.git \\\n    ../rpi-3-aarch64-demo\n(cd ../rpi-3-aarch64-demo && ./build.sh)\nBuild U-Boot for rpi_3 in the usual way\ncat ../rpi-3-aarch64-demo/armstub64.bin u-boot.bin > u-boot.bin.stubbed\nUse u-boot.bin.stubbed as kernel7.img on the Pi SD card.\n\nIn this case, the following additional entries are required in config.txt:\n\n    # Tell the FW to load the kernel image at address 0, the reset vector.\n    kernel_old=1\n\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>","distinct":true,"url":"https://api.github.com/repos/swarren/u-boot/commits/41e176d4d893a720f97a1387e6e3a25aae679d5f"}]}