public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 59818926fd9b6376537816fb071b294b73e73c32 Date: Mon, 14 Jun 2021 20:25:40 +0000 (GMT) [thread overview] Message-ID: <20210614202540.60589396E845@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via 59818926fd9b6376537816fb071b294b73e73c32 (commit) from 97390ada23198cb3849b75a17735d582919cfc46 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 59818926fd9b6376537816fb071b294b73e73c32 Author: Dimitar Dimitrov <dimitar@dinux.eu> Date: Tue Jun 1 22:45:22 2021 +0300 readings: Add PRU documents With TI official wiki gone, let's put stable links to their proprietary toolchain documents, which happen to describe ABI and instruction set. diff --git a/htdocs/readings.html b/htdocs/readings.html index 33ed5822..e75bfc49 100644 --- a/htdocs/readings.html +++ b/htdocs/readings.html @@ -256,6 +256,8 @@ names. <li>pru <br />Manufacturer: Texas Instruments + <br /><a href="https://www.ti.com/lit/ug/spruij2/spruij2.pdf">PRU Assembly Instruction User Guide.</a> + <br /><a href="https://www.ti.com/lit/ug/spruhv7c/spruhv7c.pdf">TI ABI Specification (see chapter 6).</a> <br /><a href="https://elinux.org/Category:PRU">Community PRU Documentation</a> </li> ----------------------------------------------------------------------- Summary of changes: htdocs/readings.html | 2 ++ 1 file changed, 2 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-06-14 20:25 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=20210614202540.60589396E845@sourceware.org \ --to=dimitar@sourceware.org \ --cc=gcc-cvs-wwwdocs@gcc.gnu.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: linkBe 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).