From: Abner Chang <abner.chang@hpe.com>
To: edk2-devel@lists.01.org
Subject: [staging/branch RISC-V PATCH 4/4] RiscVVirtPkg: Update README file
Date: Tue, 4 Jul 2017 13:29:24 +0800 [thread overview]
Message-ID: <1499146164-26231-5-git-send-email-abner.chang@hpe.com> (raw)
In-Reply-To: <1499146164-26231-1-git-send-email-abner.chang@hpe.com>
Update README for supporting RISC-V gcc 7.1.1.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Abner Chang <abner.chang@hpe.com>
---
RiscVVirtPkg/README | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/RiscVVirtPkg/README b/RiscVVirtPkg/README
index 64611ad..ff48f62 100644
--- a/RiscVVirtPkg/README
+++ b/RiscVVirtPkg/README
@@ -1,7 +1,7 @@
## @file
# Readme of how to build and launch RiscVVirtPkg on QEMU.
#
-# Copyright (c) 2016, Hewlett Packard Enterprise Development LP. All rights reserved.<BR>
+# Copyright (c) 2016-2017, Hewlett Packard Enterprise Development LP. All rights reserved.<BR>
#
# This program and the accompanying materials
# are licensed and made available under the terms and conditions of the BSD License
@@ -40,19 +40,23 @@ Current capabilities:
=== Get source code ===
* QEMU RISC-V PC/AT port.
- git clone https://github.com/AbnerChang/RiscVQemuPcat.git
+ git clone https://github.com/AbnerChang/RiscVQemuPcat.git (Latest commit SHA 9992f910 07/03/2017)
-* RISC-V tools
- $git clone https://github.com/riscv/riscv-tools.git (Lastest commit 419f1b5 2016/4/1)
+* RISC-V tools (RISC-V GCC 7.1.1)
+ $git clone https://github.com/riscv/riscv-tools.git (Lastest commit SHA 7cd1d105 06/22/2017)
* EDK2 open source
=== Build RISC-V tool chain ===
Before you build RISC-V tool chain, you need below packages.
-*sudo apt-get install autoconf automake autotools-dev curl libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc
+*sudo apt-get install autoconf automake autotools-dev curl device-tree-compiler libmpc-dev libmpfr-dev libgmp-dev gawk build-essential bison flex texinfo gperf libtool patchutils bc zlib1g-dev
*Change directory to riscv-tools
git submodule update --init --recursive
export RISCV=~/riscv
+*In build.sh, add build option "--with-arch=rv64g" to "build_project" as below,
+build_project riscv-gnu-toolchain --prefix=$RISCV --with-arch=rv64g
+This builds RISC-V tool chain to use RISC-V "G" varient.
+*Build RISC-V tool chain
./build.sh
The binaries needed for building EDK2 open source to RISC-V ISA are built in to ~/riscv
@@ -80,7 +84,7 @@ Before you build QEMU RISC-V EDK2, you need belwo package.
*Conf/target.txt
ACTIVE_PLATFORM = RiscVVirtPkg/RiscVVirt64.dsc
TARGET_ARCH = RISCV64
-TOOL_CHAIN_TAG = GCC53RISCV
+TOOL_CHAIN_TAG = GCC711RISCV
*$export PATH=$PATH:~/riscv/bin
*$make -C BaseTools
--
2.7.4
prev parent reply other threads:[~2017-07-04 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 5:29 [staging/branch RISC-V PATCH 0/4] RISC-V edk2 port GCC 7.1.1 Abner Chang
2017-07-04 5:29 ` [staging/branch RISC-V PATCH 1/4] RiscVPkg/Sec: Use MRET in machine trap handler Abner Chang
2017-07-04 5:29 ` [staging/branch RISC-V PATCH 2/4] BaseTools: Support RISC-V GCC 7.1.1 Abner Chang
2017-07-04 5:29 ` [staging/branch RISC-V PATCH 3/4] BaseTools: Add more RISC-V relocation types Abner Chang
2017-07-04 5:29 ` Abner Chang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1499146164-26231-5-git-send-email-abner.chang@hpe.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox