From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] af8da8: riscv64: add rv64gc bare-metal sample
Date: Wed, 26 Sep 2018 06:42:00 -0000 [thread overview]
Message-ID: <5bab2a38c5101_4e7d2ab139ea4ec0100067@hookshot-fe-da92815.cp1-iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1552 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: af8da8b181c43fe97de63c39e1d14e6c59a8950b
https://github.com/crosstool-ng/crosstool-ng/commit/af8da8b181c43fe97de63c39e1d14e6c59a8950b
Author: Paul Walmsley <paul.walmsley@sifive.com>
Date: 2018-09-24 (Mon, 24 Sep 2018)
Changed paths:
A samples/riscv64-unknown-elf/crosstool.config
A samples/riscv64-unknown-elf/reported.by
Log Message:
-----------
riscv64: add rv64gc bare-metal sample
This sample works well for building the open-source first stage
bootloader for the SiFive U540 device (and similar):
https://github.com/sifive/freedom-u540-c000-bootloader
Signed-off-by: Paul Walmsley <paul.walmsley@sifive.com>
Commit: ea1072c29ba37f29ca3f60871935aa5ca3fcb9b6
https://github.com/crosstool-ng/crosstool-ng/commit/ea1072c29ba37f29ca3f60871935aa5ca3fcb9b6
Author: Alexey Neyman <stilor@att.net>
Date: 2018-09-25 (Tue, 25 Sep 2018)
Changed paths:
A samples/riscv64-unknown-elf/crosstool.config
A samples/riscv64-unknown-elf/reported.by
Log Message:
-----------
Merge pull request #1027 from sifive/dev/paulw/rv64-bare-metal
riscv64: samples: add rv64gc bare-metal sample configuration
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/49520dbf6d55...ea1072c29ba3
**NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
reply other threads:[~2018-09-26 6:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-all 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=5bab2a38c5101_4e7d2ab139ea4ec0100067@hookshot-fe-da92815.cp1-iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).