summaryrefslogtreecommitdiffstats
path: root/src/arch/x86/cbfs_and_run.c
Commit message (Collapse)AuthorAgeFilesLines
* Add support for ram payloadsrampayloadRonald G. Minnich2018-09-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is enabled by CONFIG_RAMPAYLOAD. The code will look for a ram payload and, if it is found, try to run it. If the load fails or the payload returns it will continue with ramstage. We also include a new payload, linuxcheck, which is intended to verify that linux can be loaded and run, e.g. as a LinuxBoot payload. Currently, it fails. This does not yet work but it makes sense as a foundation on which to build. For one thing, we need to build at least a few tables for Linux. The goal for LinuxBoot is to build as few as possible. To test with linuxcheck (linux is not even close to working): cd payloads/linuxcheck/ cp x86config .config make cd ../.. make ./build/cbfstool build/coreboot.rom add-payload -n fallback/rampayload -f payloads/linuxcheck/linuxcheck.elf qemu-system-x86_64 -nographic -m 8192 -bios build/coreboot.rom -monitor /dev/pts/$1 -s We need to change the payload menu so we can add a rampayload but it's a bit tricky as written, so that must come later. Note that I'm still creating a special purpose romselfboot. The idea of merging romselfboot and selfboot is probably a good idea -- in the future. I think until we know how this should look, such a merge is premature. Signed-off-by: Ronald G. Minnich <rminnich@gmail.com> Change-Id: I8199aae6776f6dee969b370b0e6a41ef96e854d8 clang-formatted-by: Ronald G. Minnich Reviewed-on: https://review.coreboot.org/28402 Reviewed-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com> Tested-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
* arch/x86: Fix most of remaining issues detected by checkpatchLee Leahy2017-03-201-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Fix the following errors and warnings detected by checkpatch.pl: ERROR: do not use assignment in if condition ERROR: trailing statements should be on next line ERROR: Macros with complex values should be enclosed in parentheses ERROR: switch and case should be at the same indent WARNING: char * array declaration might be better as static const WARNING: else is not generally useful after a break or return WARNING: storage class should be at the beginning of the declaration WARNING: void function return statements are not generally useful WARNING: break is not useful after a goto or return WARNING: Single statement macros should not use a do {} while (0) loop WARNING: sizeof *t should be sizeof(*t) WARNING: Comparisons should place the constant on the right side of the test TEST=Build and run on Galileo Gen2 Change-Id: I39d49790c5eaeedec5051e1fab0b1279275f6e7f Signed-off-by: Lee Leahy <Leroy.P.Leahy@intel.com> Reviewed-on: https://review.coreboot.org/18865 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com>
* tree: drop last paragraph of GPL copyright headerPatrick Georgi2015-10-311-4/+0
| | | | | | | | | | | | | | | | It encourages users from writing to the FSF without giving an address. Linux also prefers to drop that and their checkpatch.pl (that we imported) looks out for that. This is the result of util/scripts/no-fsf-addresses.sh with no further editing. Change-Id: Ie96faea295fe001911d77dbc51e9a6789558fbd6 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-on: http://review.coreboot.org/11888 Tested-by: build bot (Jenkins) Reviewed-by: Alexandru Gagniuc <mr.nuke.me@gmail.com> Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
* x86: flatten hierarchy4.14.1Stefan Reinauer2015-07-131-0/+26
It never made sense to have bootblock_* in init, but pirq_routing.c in boot, and some ld scripts on the main level while others live in subdirectories. This patch flattens the directory hierarchy and makes x86 more similar to the other architectures. Change-Id: I4056038fe7813e4d3d3042c441e7ab6076a36384 Signed-off-by: Stefan Reinauer <stefan.reinauer@coreboot.org> Reviewed-on: http://review.coreboot.org/10901 Tested-by: build bot (Jenkins) Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com> Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>