{"push_id":1013852449,"size":12,"distinct_size":12,"ref":"refs/heads/master","head":"deff6fb3a7790e93264292982000275e78bb12e5","before":"08b24722f0ac9159697360faed35d12852592eb3","commits":[{"sha":"c6c7eed741981e12111ef6fa25265cc5f0b53908","author":{"email":"378b411a8a63ecc7605ec4272234862d7781c6ae@socionext.com","name":"Masahiro Yamada"},"message":"ARM: uniphier: document how-to-build for Ace and Sanji boards\n\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/c6c7eed741981e12111ef6fa25265cc5f0b53908"},{"sha":"51244a60805fb91112f61ef268f58fc6d47a3d0a","author":{"email":"378b411a8a63ecc7605ec4272234862d7781c6ae@socionext.com","name":"Masahiro Yamada"},"message":"ARM: uniphier: fix build error when CONFIG_CMD_DDRMPHY_DUMP=y\n\nThe build fails if compiled with CONFIG_CMD_DDRMPHY_DUMP=y since commit\n46abfcc99e04 (\"ARM: uniphier: rework struct uniphier_board_data\").\n\nFixes: 46abfcc99e04 (\"ARM: uniphier: rework struct uniphier_board_data\")\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/51244a60805fb91112f61ef268f58fc6d47a3d0a"},{"sha":"fdd15b6a86312c2878f3c7a83c70bcf66bbd56a6","author":{"email":"378b411a8a63ecc7605ec4272234862d7781c6ae@socionext.com","name":"Masahiro Yamada"},"message":"pinctrl: uniphier: set input-enable before pin-muxing\n\nWhile IECTRL is disabled, input signals are pulled-down internally.\nIf pin-muxing is set up first, glitch signals (Low to High transition)\nmight be input to hardware blocks.\n\nBad case scenario:\n[1] The hardware block is already running before pinctrl is handled.\n   (the reset is de-asserted by default or by a firmware, for example)\n[2] The pin-muxing is set up.  The input signals to hardware block\n   are pulled-down by the chip-internal biasing.\n[3] The pins are input-enabled.  The signals from the board reach the\n    hardware block.\n\nActually, one invalid character is input to the UART blocks for such\nSoCs as PH1-LD4, PH1-sLD8, where UART devices start to run at the\npower on reset.\n\nTo avoid such problems, pins should be input-enabled before muxing.\n\n[ ported from Linux commit bac7f4c1bf5e7c6ccd5bb71edc015b26c77f7460 ]\n\nFixes: 5dc626f83619 (\"pinctrl: uniphier: add UniPhier pinctrl core support\")\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/fdd15b6a86312c2878f3c7a83c70bcf66bbd56a6"},{"sha":"1d22c4b1bdb169850736849ac100d7822512b6fb","author":{"email":"378b411a8a63ecc7605ec4272234862d7781c6ae@socionext.com","name":"Masahiro Yamada"},"message":"pinctrl: uniphier: guard uniphier directory with CONFIG_PINCTRL_UNIPHIER\n\nCONFIG_PINCTRL_UNIPHIER is more suitable than CONFIG_ARCH_UNIPHIER\nto guard the drivers/pinctrl/uniphier directory.\n\nThe current CONFIG_PINCTRL_UNIPHIER_CORE is a bit long, so rename it\ninto CONFIG_PINCTRL_UNIPHIER.\n\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/1d22c4b1bdb169850736849ac100d7822512b6fb"},{"sha":"5d07648662edf2b994a6433465d472a9a3e89923","author":{"email":"378b411a8a63ecc7605ec4272234862d7781c6ae@socionext.com","name":"Masahiro Yamada"},"message":"ARM: uniphier: allow debug_ll_init() to do nothing for unknown SoCs\n\nThis function should just return for unknown SoCs rather than writing\nunexpected values to registers.\n\nSigned-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/5d07648662edf2b994a6433465d472a9a3e89923"},{"sha":"138daa7b363926b17095e4960853dee12f30aac9","author":{"email":"353bab2838e404dd1b05159a10c4c35edf2cee68@gmail.com","name":"Derald D. Woods"},"message":"OMAP3: am3517_evm: Use BCH8 ECC for NAND\n\nSelect 8-bit BCH ecc-scheme with s/w based error correction\n- OMAP_ECC_BCH8_CODE_HW_DETECTION_SW\n\nSigned-off-by: Derald D. Woods <woods.technical@gmail.com>\nReviewed-by: Tom Rini <trini@konsulko.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/138daa7b363926b17095e4960853dee12f30aac9"},{"sha":"3f53e619f0d72db7b5812313c8f290051c7bfbee","author":{"email":"353bab2838e404dd1b05159a10c4c35edf2cee68@gmail.com","name":"Derald D. Woods"},"message":"OMAP3: am3517_evm: Add NAND MTD partitions with UBI/UBIFS support\n\n- Add required UBI/UBIFS config definitions\n- Add reasonable MTD partition layout\n- Remove JFFS2 config definitions\n- Drop some CFI verbage and definitions\n- Make comment 'one-liners' truly one line\n- Improve readability and content arrangement\n\nSigned-off-by: Derald D. Woods <woods.technical@gmail.com>\nReviewed-by: Tom Rini <trini@konsulko.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/3f53e619f0d72db7b5812313c8f290051c7bfbee"},{"sha":"22aa61f707574dd569296f521fcfc46a05f51c48","author":{"email":"58cabfb725bce47f8693cd75994b158451973fe2@gmail.com","name":"Stanislav Galabov"},"message":"api: Export API structure address as an environment variable\n\nThis patch makes the U-Boot api export its structure address as an environment\nvariable, so it can be used to directly hint FreeBSD's loader of api's location.\n\nThe relevant FreeBSD loader change is currently under review at:\nhttps://reviews.freebsd.org/D5492\n\nSigned-off-by: Stanislav Galabov <sgalabov@gmail.com>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/22aa61f707574dd569296f521fcfc46a05f51c48"},{"sha":"22d90d560a2b01c47f180e196e6c6485eb8e65db","author":{"email":"3ad82b0c937b9aa51276120cedd545efc822be04@suse.de","name":"Alexander Graf"},"message":"omap3: Use raw SPL by default for mmc1\n\nNow that we fall back to the FS code path when we don't find u-boot\nat the raw sector offset, there is no good reason to not default to\nraw boot.\n\nWith this patch, I can successfully boot u-boot from a raw sector\noffset on beagle-xm.\n\nSigned-off-by: Alexander Graf <agraf@suse.de>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/22d90d560a2b01c47f180e196e6c6485eb8e65db"},{"sha":"699946ae61d52547113ccfc5bdca116d4ade3c6f","author":{"email":"47764aff062bf9ebe98a2274b29052b74a9567e2@konsulko.com","name":"Tom Rini"},"message":"sandbox: Fix building with LLVM\n\n- The macro __BIGGEST_ALIGNMENT__ is gcc-specific.  If it is not defined\n  we'll just assume 16.  This is correct for at least the common cases\n  and LLVM does not provide an equivalent macro.\n- When linking U-Boot we're passing -T to the linker, and while gcc will\n  just pass this along with LLVM we need to be specific.\n\nCc: Simon Glass <sjg@chromium.org>\nSigned-off-by: Tom Rini <trini@konsulko.com>\nReviewed-by: Simon Glass <sjg@chromium.org>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/699946ae61d52547113ccfc5bdca116d4ade3c6f"},{"sha":"2f0bcd4de1ab0cb03f01428a334cd91f8870504c","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"malloc: use hidden visibility\n\nWhen running sandbox, the following phases occur, each with different\nmalloc implementations or behaviors:\n\n1) Dynamic linker execution, using the dynamic linker's own malloc()\nimplementation. This is fully functional.\n\n2) After U-Boot's malloc symbol has been hooked into the GOT, but before\nany U-Boot code has run. This phase is entirely non-functional, since\nU-Boot's gd symbol is NULL and U-Boot's initf_malloc() and\nmem_malloc_init() have not been called.\n\nAt least on Ubuntu Xenial, the dynamic linker does make both malloc() and\nfree() calls during this phase. Currently these free() calls crash since\nthey dereference gd, which is NULL.\n\nU-Boot itself makes no use of malloc() during this phase.\n\n3) U-Boot execution after gd is set and initf_malloc() has been called.\nThis is fully functional, albeit via a very simple malloc()\nimplementation.\n\n4) U-Boot execution after mem_malloc_init() has been called. This is fully\nfunctional with a complete malloc() implementation.\n\nFurthermore, if code that called malloc() during phase 1 calls free() in\nphase 3 or later, it is likely that heap corruption will occur, since\nU-Boot's malloc implementation will assume the pointer is part of its own\nheap, although it isn't. I have not actively observed this happening.\n\nTo prevent phase 2 from happening, this patch makes all of U-Boot's malloc\nlibrary public symbols have hidden visibility. This prevents them from\nbeing hooked into the GOT, so only code in the U-Boot binary itself\nactually calls them; any other code will call into the standard C library\nmalloc(). This also avoids the \"furthermore\" issue mentioned above.\n\nI have seen references to this GCC pragma in blog posts from 2008, and\nRHEL5's ancient gcc appears to accept it fine, so I believe it's quite\nsafe to use it without checking gcc version.\n\nCc: Rabin Vincent <rabin@rab.in>\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\nReviewed-by: Simon Glass <sjg@chromium.org>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/2f0bcd4de1ab0cb03f01428a334cd91f8870504c"},{"sha":"deff6fb3a7790e93264292982000275e78bb12e5","author":{"email":"5ef2a23ba3aff51d1cfc8c113c1ec34b608b3b13@wwwdotorg.org","name":"Stephen Warren"},"message":"malloc: remove !gd handling\n\nFollowing the previous patch, malloc() is never called before gd is set,\nso we can remove the special-case check for this condition.\n\nThis reverts commit 854d2b9753e4 \"dlmalloc: ensure gd is set for early\nalloc\".\n\nCc: Rabin Vincent <rabin@rab.in>\nSigned-off-by: Stephen Warren <swarren@wwwdotorg.org>\nReviewed-by: Tom Rini <trini@konsulko.com>\nReviewed-by: Simon Glass <sjg@chromium.org>","distinct":true,"url":"https://api.github.com/repos/qemu/u-boot/commits/deff6fb3a7790e93264292982000275e78bb12e5"}]}