On Tue, Aug 14, 2018 at 2:39 PM, Christian Gmeiner <christian.gmei...@gmail.com> wrote: > Am Fr., 10. Aug. 2018 um 11:37 Uhr schrieb Bin Meng <bmeng...@gmail.com>: >> >> Currently building U-Boot as the coreboot payload requires user >> to change the build configuration for a specific board during >> menuconfig process. This uses the board's native device tree >> to configure the hardware. For example, the device tree provides >> PCI address range for the PCI host controller and U-Boot will >> re-program all PCI devices' BAR to be within this range. In order >> to make sure we don't mess up the hardware, we should guarantee >> the range matches what coreboot programs the chipset. >> >> But we really should make the coreboot payload support easier. >> Just like EFI payload, we can create a generic coreboot payload >> for all x86 boards as well. The payload is configured to include >> as many generic drivers as possible. All stuff that touches low >> level initialization are not allowed as such is the coreboot's >> responsibility. Platform specific drivers (like gpio, spi, etc) >> are not included. >> >> Signed-off-by: Bin Meng <bmeng...@gmail.com> > > I really love this generic coreboot payload thing and should simplify the > stuff I am working on ( - a generic coreboot payload with some boot logic > stuff in it). > > Reviewed-by: Christian Gmeiner <christian.gmei...@gmail.com>
applied to u-boot-x86, thanks! _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
