aboutsummaryrefslogtreecommitdiff
path: root/Makefile.in
AgeCommit message (Collapse)AuthorFilesLines
2020-10-31Disable device tree filter when load a dts from file (#219)Yan1-0/+4
* add device tree in elf, using --with-dts to add the absolute path of device tree * Disable device tree filter * Remove *.dtb dependence, when the --with-dts option is not used
2020-10-30Revert "Disable device tree filter when load a dts from file (#217)"Andrew Waterman1-4/+0
This reverts commit a161e6f3ef31004e47a5b94b85c2e84b764f8637. Resolves #218
2020-10-29Disable device tree filter when load a dts from file (#217)Yan1-0/+4
* add device tree in elf, using --with-dts to add the absolute path of device tree * Disable device tree filter
2020-04-28Support --without-payload for OpenSBI fw_jump-style booting (#186)Jessica Clarke1-1/+4
We expect the firmware to load the external payload at the second megapage, and that there is space to put the filtered FDT at 0x2200000 past the start of memory. With a default MEM_START of 0x80000000, this matches the standard OpenSBI values for FW_JUMP_ADDR and FW_JUMP_FDT_ADDR of 0x80400000/0x80200000 (RV32/RV64) and 0x82200000 respectively, so payloads linked for one should work with the other.
2019-12-09Added --with-abi configure option (#183)Nick Knight1-4/+13
* Added --with-abi configure option * Revised to preserve original semantics when user specifies --with-arch but not --with-abi or when the user specifies --with-arch but not --host.
2019-10-22Merge pull request #150 from lsgunth/build_fixesAndrew Waterman1-5/+6
Build fixes
2019-10-18Add user write permissions to installed filesAndrew Waterman1-2/+2
2019-06-11configure: Add option to set physical memory start addressGabriel L. Somlo1-1/+1
For systems where physical memory is mapped to a start address different from 0x80000000, allow the default to be overridden using the --with-mem-start argument to the configure script. Signed-off-by: Gabriel Somlo <gsomlo@gmail.com>
2019-03-22Always build bbl.binLogan Gunthorpe1-3/+4
bbl.bin is necessary for booting on hardware and is created by a simple objcopy line. It's much more convienent for riscv-pk to create this file then to expect the user to know to do it or to dig through the SDK's makefile to learn that it's required. Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
2019-03-22Disable compiler protections featuresLogan Gunthorpe1-2/+2
The riscv compiler available in Ubuntu enables stack protection and FORTIFY source by default which breaks the build. Adding -fno-stack-protector and -U_FORTIFY_SOURCE to the tool flags fixes this without any side effects. The compiler available in debian do not have these protections enabled and work with or without the extra flag. Fixes: #105 Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
2019-01-15Revert "Don't require a RISC-V libc and crt when configuring (#132)" (#140)Andrew Waterman1-1/+1
This reverts commit a02257a861a4d13f31868a27c197cfc5576101e1.
2019-01-04Don't require a RISC-V libc and crt when configuring (#132)James Clarke1-1/+1
2018-07-26Fix stubs-lp64.h/stubs-lp64d.h/stubs-ilp32.h/stubs-ilp32d.h not foundZong Li1-6/+3
For now, we always compile files with -mabi option by using soft-fp ABI. But there are some files use the header which in toolchain, like unistd.h, stdint.h and so on. Finally, these header files include other header files which existing depend on ABI such as stubs-lp64.h or stubs-lp64d.h. So it causes the header file not found when using the double-float toolchain with soft-float ABI. Fix up by compiling files with -march and -mabi options only if there is specifying the --with-arch option at configure time. If use the --with-arch option at configure time, that means your toolchain has multi-lib support, so always building riscv-pk by soft-float ABI is fine. Otherwise, we don't compile files with specifying march and mabi options explicitly
2018-07-09Properly license all nontrivial filesAndrew Waterman1-0/+2
2018-06-21Replace the --enable-32bit option by --with-archZong Li1-3/+21
Get rid of the --enable-32bit option and switch to use --with-arch, which is more standard because it matches the GCC build. If --with-arch is not specified, it defaults to whatever the compiler's default is. The --with-abi is not necessary for this project. Unconditionally compile it with a no-float ABI.
2017-11-03Fix line endings in the logoPalmer Dabbelt1-1/+1
2017-11-03Allow users to pick a logoPalmer Dabbelt1-1/+1
2017-02-20Don't block for acks on console writesAndrew Waterman1-2/+4
2016-07-16Support 32bit build (#27)Prashanth Mundkur1-1/+1
* Support configuration for a 32-bit build. * Regenerate configure.
2016-03-09Refactor pk, bbl, machine into separate librariesAndrew Waterman1-3/+4
Yuck.
2015-09-02Don't automatically run autoconfAndrew Waterman1-9/+0
Run it yourself if you modify configure.ac, and commit the configure script.
2015-05-18Change the behavior of the DESTDIR make variablePalmer Dabbelt1-5/+5
DESTDIR is a common make idiom. As per the GNU coding standards https://www.gnu.org/prep/standards/html_node/DESTDIR.html "DESTDIR is a variable prepended to each installed target file, like this: $(INSTALL_PROGRAM) foo $(DESTDIR)$(bindir)/foo $(INSTALL_DATA) libfoo.a $(DESTDIR)$(libdir)/libfoo.a The DESTDIR variable is specified by the user on the make command line as an absolute file name. For example: make DESTDIR=/tmp/stage install DESTDIR should be supported only in the install* and uninstall* targets, as those are the only targets where it is useful. If your installation step would normally install /usr/local/bin/foo and /usr/local/lib/libfoo.a, then an installation invoked as in the example above would install /tmp/stage/usr/local/bin/foo and /tmp/stage/usr/local/lib/libfoo.a instead." The current Makefile.in uses DESTDIR, but has a slightly non-standard behavior: the target install location doesn't include "$prefix". This breaks package managers, because stuff ends up getting installed to the wrong location. Unfortunately the only way I can think of to fix this involves silently changing the behavior of DESTDIR. Hopefully nobody is using it...? [port of 8a2088b59162fe16c16d26ddc1cfcaaaa8c4156f in riscv-fesvr]
2015-05-10Split pk functionality into pk and bblAndrew Waterman1-6/+6
pk is now an AEE only (i.e. it can only execute user programs). bbl is now an SEE only (i.e. it can only host kernels).
2014-10-26Don't rely on the C libraryAndrew Waterman1-1/+1
2012-08-30respect CFLAGS and LDFLAGS env varsChristopher Celio1-2/+2
2011-06-19temporary undoing of renamingAndrew Waterman1-0/+461
2011-06-19Renamed packagesAndrew Waterman1-461/+0
2011-04-15[pk] load pk at addr 0; user stack top = MEMSIZEAndrew Waterman1-6/+6
2010-11-21[opcodes, pk, sim, xcc] made jumps shorter and PC-relativeAndrew Waterman1-1/+1
2010-10-15[pk, sim] added FPU emulation support to proxy kernelAndrew Waterman1-13/+13
2010-08-18[pk,fesvr] improved proxykernel build systemAndrew Waterman1-0/+461
Now uses a modified MCPPBS. Add --host=riscv to configure path. Front-end server now just searches PATH for riscv-pk, so just install the pk to somewhere in your path.
generated by cgit v1.1 at 2024-07-16 16:59:28 +0000