summaryrefslogtreecommitdiff
path: root/resources/u-boot
AgeCommit message (Collapse)Author
2022-08-29u-boot: Add veyron jerry chromebook configsAlper Nebi Yasak
This adds U-Boot configuration for a few white-label chromebooks, known as "chromebook_jerry" in the U-Boot upstream defconfigs. It uses the shared tree for the "veyron" baseboard. The config is almost the same as upstream defconfig, but with REMAKE_ELF and POSITION_INDEPENDENT enabled. Untested since I don't have any of the veyron jerry chromebooks. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-29u-boot: Add veyron minnie chromebook configsAlper Nebi Yasak
This adds U-Boot configuration for the ASUS Chromebook Flip C100PA, also known as "chromebook_minnie" in the U-Boot upstream defconfigs. It uses the shared tree for the "veyron" baseboard. The config is almost the same as upstream defconfig, but with REMAKE_ELF and POSITION_INDEPENDENT enabled. Untested since I don't have the veyron minnie chromebook. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-29u-boot: Add veyron speedy chromebook configsAlper Nebi Yasak
This adds U-Boot configuration for the ASUS Chromebook C201PA, also known as "chromebook_speedy" in the U-Boot upstream defconfigs. Also adds a shared "veyron" board directory to share with others having the same baseboard. The config is almost the same as upstream defconfig, but with REMAKE_ELF and POSITION_INDEPENDENT enabled. Untested since I don't have the veyron speedy chromebook. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-29u-boot: Add bob chromebook configsAlper Nebi Yasak
This adds U-Boot configuration for the ASUS Chromebook Flip C101, also known as "chromebook_bob" in the U-Boot upstream defconfigs. It uses the shared tree for the "gru" baseboard. The config has the following diffconfig from kevin: # chromebook_bob instead of chromebook_kevin DEFAULT_DEVICE_TREE "rk3399-gru-kevin" -> "rk3399-gru-bob" DEFAULT_FDT_FILE "rockchip/rk3399-gru-kevin.dtb" -> "rockchip/rk3399-gru-bob.dtb" OF_LIST "rk3399-gru-kevin" -> "rk3399-gru-bob" SPL_OF_LIST "rk3399-gru-kevin" -> "rk3399-gru-bob" TARGET_CHROMEBOOK_BOB n -> y TARGET_CHROMEBOOK_KEVIN y -> n # Display resolution is 1280x800, and no need for the big font VIDEO_FONT_8X16 n -> y VIDEO_FONT_TER16X32 y -> n VIDEO_ROCKCHIP_MAX_XRES 2400 -> 1280 VIDEO_ROCKCHIP_MAX_YRES 1600 -> 800 Untested since I don't have the bob chromebook. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-28u-boot: Add kevin chromebook configsAlper Nebi Yasak
This adds U-Boot configuration for the Samsung Chromebook Plus (v1), also known as "chromebook_kevin" in the U-Boot upstream defconfigs. Also adds a shared "gru" board directory to share with others having the same baseboard. It uses v2022.07 with some quality-of-life patches. The first one is a clock adjustment to match coreboot clocks for the video output, the second one is a series about text cursor support and larger fonts. These are because the display has a high resolution of 2400x1600 at 12.3". The config has the following diffconfig from the upstream defconfig for this board: # For chainloading from depthcharge like a payload (RW_LEGACY). # Not everything might be necessary, but didn't test without these. INIT_SP_RELATIVE n -> y LNX_KRNL_IMG_TEXT_OFFSET_BASE 0x00200000 -> 0x18000000 POSITION_INDEPENDENT n -> y SYS_TEXT_BASE 0x00200000 -> 0x18000000 +SYS_INIT_SP_BSS_OFFSET 524288 # Higher speeds for eMMC MMC_HS200_SUPPORT n -> y MMC_HS400_ES_SUPPORT n -> y MMC_HS400_SUPPORT n -> y MMC_IO_VOLTAGE n -> y MMC_SDHCI_SDMA n -> y MMC_SPEED_MODE_SET n -> y +MMC_UHS_SUPPORT y # Build the u-boot.elf to use as a payload REMAKE_ELF n -> y # Slightly faster video output VIDEO_COPY n -> y # Larger fonts per the applied series VIDEO_FONT_8X16 y -> n VIDEO_FONT_TER16X32 n -> y Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-27u-boot-libre: Add support for deblobbing U-Boot v2022.07Alper Nebi Yasak
Add a 'v2022.07' pseudo-board for the U-Boot download script with the default blobs list, and mark the version as supported in u-boot-libre release script. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-27download/u-boot: Support reading tree and revision from board.cfgAlper Nebi Yasak
Boards may want to specify a board-specific U-Boot revision. At the very least, pseudo-boards for u-boot-libre releases will need to specify their U-Boot versions somehow. Copy the existing mechanism from download/coreboot for specifying build info with board.cfg files. Specify the commit hash for the 'v2021.07' pseudo-board, and 'master' as the default. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-27download/u-boot: Prepare files per board instead of per revisionAlper Nebi Yasak
The U-Boot download script is designed to help with releasing u-boot-libre and it can only prepare a generic U-Boot v2021.07 tree. However, we will need to build board-specific versions of U-Boot to be able to use it as a coreboot payload effectively. As a first step toward that, make the download script prepare per-board copies of U-Boot v2021.07. Then, add a 'v2021.07' pseudo-board for the u-boot-libre release script to work on. The u-boot-libre deblob script hash ends up chaning due to copying my author attribution from the download script, update its hash. Signed-off-by: Alper Nebi Yasak <alpernebiyasak@gmail.com>
2022-08-25u-boot-libre: remove nonfree firmware in drivers/dma/MCD_tasks.cDenis 'GNUtoo' Carikli
This firmware lack corresponding source code. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
2022-02-10Add support for releasing deblobbed u-boot 2020.07 source tarballsDenis 'GNUtoo' Carikli
Once the tarball are released, it will enable distributions to use these tarballs to produce deblobbed u-boot packages. Note that the produced tarball is not reproducible yet. Because of that it has to be trusted. During a release, it's a good idea to sign the uncompressed tarball as the various compression formats and associated tools make different tradeoffs. For instance with xz, xz -9e tends to compress really well with the the most used xz[1] implementation, and most GNU/Linux users probably already have it installed, but and the drawbacks is that the format is very fragile[2]. The lzip format is more suited for long term archiving but its most packaged implementation[3] is less likely to be already installed by users than more well known formats like xz, bzip2 or gzip. Being able to add more compression formats after the release is also useful, for instance to accommodate different build systems or use cases (like being able to build u-boot with less dependencies in distributions like Guix, or building u-boot directly on devices which don't have enough RAM for xz for instance). [1]https://tukaani.org/xz/ [2]https://www.nongnu.org/lzip/xz_inadequate.html [3]https://www.nongnu.org/lzip/ Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>