| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | bios_emulator: Add vesa support and allow ROMs to be passed in as data | Simon Glass | 2014-11-25 | 1 | -0/+8 |
| | | | | | | | | | | As well as locating the ROM on the PCI bus, allow the ROM to be supplied to the emulator. Split the init up a little so that callers can supply their own interrupt routines. Also allow a vesa mode to be provided, to be selected once the BIOS run is complete. Signed-off-by: Simon Glass <sjg@chromium.org> | ||||
| * | pci: Add general support for execution of video ROMs | Simon Glass | 2014-11-25 | 1 | -0/+15 |
| | | | | | | | | | | | | | | | | | | | Some platforms don't have native code for dealing with their video hardware. In some cases they use a binary blob to set it up and perform required actions like setting the video mode. This approach is a hangover from the old PC days where a ROM was provided and executed during startup. Even now, these ROMs are supplied as a way to set up video. It avoids the code for every video chip needing to be provided in the boot loader. But it makes the video much less flexible - e.g. it is not possible to do anything else while the video init is happening (including waiting hundreds of milliseconds for display panels to start up). In any case, to deal with this sad state of affairs, provide an API for execution of x86 video ROMs, either natively or through emulation. Signed-off-by: Simon Glass <sjg@chromium.org> | ||||
| * | Introduce a header file for the BIOS emulator | Simon Glass | 2014-11-25 | 1 | -0/+43 |
| We should have a public header so that users can avoid defining functions themselves. Signed-off-by: Simon Glass <sjg@chromium.org> | |||||
 |
index : blackbird-obmc-uboot | |
| Blackbird™ U-Boot sources for OpenBMC | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|