So that you can use virtio network, block etc create the virtio mmio instances. There are 128 of these even if they are not all used, a single mmio base value is passed via bootinfo. Reviewed-by: Angelo Dureghello <angelo@kernel-space.org> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Kuan-Wei Chiu <visitorckw@gmail.com> Tested-by: Kuan-Wei Chiu <visitorckw@gmail.com> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
In Linux these are meant to read a little-endian value and swap to the CPU endian. In u-boot for m68k this is currently broken and prevents virtio-mmio from functioning. This change is only for classic m68k. Coldfire has read big-endian, no swap for these in u-boot and Linux and existing drivers probably depend on this. Tested-by: Angelo Dureghello <angelo@kernel-space.org> Reviewed-by: Simon Glass <sjg@chromium.org> Acked-by: Kuan-Wei Chiu <visitorckw@gmail.com> Acked-by: Angelo Dureghello <angelo@kernel-space.org> Signed-off-by: Daniel Palmer <daniel@thingy.jp>
There is a value of 256K hardcoded as u-boot image size. This produce bank tty as soon as the image size grows over the limit. Fix it by using value preset by CONFIG_SYS_MONITOR_LEN. Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
Some NXP imx hardware ip module as the esdhc controller are exactly the same in some new ColdFire cpus. For the specific case, mcf5441x needs to use the existing fsl_esdhc_imx.c driver for the esdhc device. Create a stub to be able to use NXP "imx" serie drivers as the fsl_esdhc_imx in the ColdFire architecture. Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
Enable esdhc device. Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
Add mmc support for the mcf5441x family. There is only one esdhc controller for this cpu family. Signed-off-by: Angelo Dureghello <angelo@kernel-space.org>
This series from Daniel Palmer <daniel@0x0f.com> improves debug UART support on QEMU on M68K by adding debug uart support to the serial driver. Link: https://lore.kernel.org/r/20260309105110.672832-1-daniel@0x0f.com
Once the stack is ready we can init the debug uart to help with debugging so do that. Signed-off-by: Daniel Palmer <daniel@0x0f.com> Acked-by: Angelo Dureghello <angelo@kernel-space.org>
Simon Glass <sjg@chromium.org> says: Each arch does something slightly different before booting the OS. Some archs even do different things depending on the CPU type. It is quite hard to know what actually happens in the final milliseconds before the OS boot. This series attempts to start cleaning up U-Boot in this area. The basic intent is to create a new bootm_final() function which can be called by all archs. It provides some flags for a couple of necessary variations but otherwise it is generic. All architectures are converted over to use this new function. board_quiesce_devices() is moved into bootm_final() so that all archs benefit from it. This series fixes a bug in device_remove() is fixed where removing a parent with specialised flags (e.g. DM_REMOVE_ACTIVE_ALL) could leave children activated, since they do not match the flags. This fixes is needed to avoid bootm_final() causing test failures on sandbox. Future work could take this a little further: - Convert EFI loader to use the same function - Improve comments for cleanup_before_linux() across architectures - Support fake-run tracing on all archs Link: https://lore.kernel.org/r/20260306023638.2678886-1-sjg@chromium.org
Add a call to bootm_final() before jumping to the kernel. This adds the "Starting kernel" message, bootstage tracking, board_quiesce_devices() and dm_remove_devices_active() which were not previously called on m68k. Signed-off-by: Simon Glass <simon.glass@canonical.com> Acked-by: Angelo Dureghello <angelo@kernel-space.org> Tested-by: Angelo Dureghello <angelo@kernel-space.org> Acked-by: Kuan-Wei Chiu <visitorckw@gmail.com>