![]() ![]() With the change to only init video devices that are present in the stdoutĮnvironment variable, this fails. This code currently always selects the second source. ` (20 subsequent siblings) 21 siblings, 1 reply 47+ messages in thread ![]() 21:21 ` rockchip: video: Correct VOP clock selection Simon Glass 21:21 rockchip: Add support for Asus Chromebit Simon 21:21 ` Simon Glass * rockchip: video: Correct HDMI data source selection.Rockchip: Add support for veyron-mickey (Chromebit)Īrch/arm/dts/rk3288-veyron-chromebook.dtsi | 2 + Rockchip: video: Avoid using u8 in the HDMI driver Rockchip: veyron: Adjust ARM clock after relocation Rockchip: Move jerry SDRAM settings into its own. Rockchip: veyron: Add a note about the SDRAM voltage Video: Use cache-alignment in video_sync() Spi: Add error checking for invalid bus widths Rockchip: spi: Honour the deactivation delay Rockchip: spi: Add support for of-platdata Spi: Add of-platdata support to SPI and SPI flash ![]() Stdio: Correct numbering logic in stdio_probe_device() Rockchip: video: Correct VOP clock selectionĭm: core: Handle global_data moving in SPL Rockchip: video: Correct HDMI data source selection Add new patch to avoid using u8 in the HDMI driver Add new patch with note about the SDRAM voltage Not seem necessary with mickey, so instead, this is done in U-Boot proper.Īdditionally some bugs have crept in as part of the clock API conversionĪnd other work, so this series fixes those. SomeĬurrently there is an option to increase the CPU speed in SPL. If both HDMI and EDP try to use the same video-out device (VOP). Jerry supportsīoth its internal EDP display and HDMI. SPI is used to boot, and we move jerry toĪt present there are few boards in U-Boot with two displays. RK3288-based Chromebooks will use the 'veyron' board, with everythingĬommon except the device tree. Some refactoring is included to jerry also. This series adds support for 'mickey', the Asus Chromebit based on Rockchip ` (21 more replies) 0 siblings, 22 replies 47+ messages in thread 21:21 ` rockchip: video: Correct HDMI data source selection Simon Glass Sauvegarde du firmware initial : : Add support for Asus Chromebit All of help / color / mirror / Atom feed * rockchip: Add support for Asus Chromebit 21:21 Simon Glass You may need to adjust slightly for your distro, but these instructions should work in most cases. What we're doing is copying the grub EFI boot stub from the OS installed location to the location the firmware is expecting (/EFI/BOOT/BOOTX64.efi) on the EFI system partition (ESP), which most (Debian/Ubuntu-based?) distros will mount at /boot/efi. Once your OS is booted, open a terminal/shell, and type the following (observing case):Ĭp /boot/efi/EFI//grub圆4.efi /boot/efi/EFI/BOOT/BOOTX64.efi From there, select Boot From File, then navigate to and boot from /EFI//grub圆4.efi (where will be ubuntu, arch, debian, etc). Type 'exit' to return to the UEFI settings menu, then select Boot Maintenance Manager. I'm using your UEFI firmware, installed my OS, and it still boots to the EFI shell - what do I do?Ī: Sounds like your Linux distro doesn't install the EFI bootloader in the default location - no worries, it's an easy fix: Ensuite, il a fallu suivre cette résolution de pb : ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |