From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Subject: [pushed] wwwdocs: readings: Update MicroBlaze Processor Reference reference
Date: Thu, 9 Feb 2023 08:50:58 +0100 (CET) [thread overview]
Message-ID: <20230209075101.2699033E6A@hamza.pair.com> (raw)
Second link this week that actually shorter - wooo...
Pushed.
Gerald
---
htdocs/readings.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 29368a9a..34ba508c 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -193,7 +193,7 @@ names.
<li>MicroBlace
<br>Manufacturer: Xilinx
- <br><a href="https://www.xilinx.com/support/documentation/sw_manuals/xilinx11/mb_ref_guide.pdf">
+ <br><a href="https://www.xilinx.com/htmldocs/xilinx11/mb_ref_guide.pdf">
MicroBlaze Processor Reference Guide</a>
<br>GDB includes a simulator for an earlier version of the processor.
</li>
--
2.39.1
reply other threads:[~2023-02-09 7:51 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=20230209075101.2699033E6A@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@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: 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).