Update links to point to new Trusted Firmware host.
Also add link to bug dashboard.
Change-Id: Id06e331bb0992bff4e29905c7dc08e85c618fea2
Signed-off-by: Andrew Walbran <qwandor@google.com>
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index d90abc9..f6c08b7 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -10,7 +10,7 @@
## Code reviews
All submissions, including submissions by project members, require review. We
-use [Gerrit](https://hafnium-review.googlesource.com) for this purpose.
+use [Gerrit](https://review.trustedfirmware.org/) for this purpose.
To submit a change:
@@ -36,12 +36,12 @@
9. If you changed submodules, then add a matching 'topic' from the Gerrit UI
for all your changes (submodules and the main repository) so that they can
be reviewed and submitted together.
-10. Wait 10-15 minutes for our presubmit tests to run, and make sure a 'Kokoro
+10. Wait 20-30 minutes for the presubmit tests to run, and make sure a 'Verified
+1' comment shows up in Gerrit indicating that they have passed. If not,
follow the links to find the errors, fix them and try again.
11. From the Gerrit UI add one or more reviewers. Looking at who has modified
the same files frequently recently is usually a good way to pick a reviewer,
- but if you're not sure then you can add hafnium-team@google.com.
+ but if you're not sure then you can add hafnium@lists.trustedfirmware.org.
## Community Guidelines
diff --git a/README.md b/README.md
index 5ee74bf..0d7d266 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,9 @@
Hafnium is a hypervisor, initially supporting aarch64 (64-bit Armv8 CPUs).
Get in touch and keep up-to-date at
-[hafnium-discuss@googlegroups.com](https://groups.google.com/forum/#!forum/hafnium-discuss).
+[hafnium@lists.trustedfirmware.org](https://lists.trustedfirmware.org/mailman/listinfo/hafnium).
+See feature requests and bugs on our
+[bug dashboard](https://developer.trustedfirmware.org/project/21/item/view/67/).
## Getting started
diff --git a/docs/FVP.md b/docs/FVP.md
index 6a34f0f..8790bee 100644
--- a/docs/FVP.md
+++ b/docs/FVP.md
@@ -22,19 +22,18 @@
$ make && kokoro/test.sh --fvp
```
-See the `fvp` function in
-[`hftest.py`](http://cs/hafnium/test/hftest/hftest.py?q=symbol:fvp) for details
+See the `FvpDriver` class in [`hftest.py`](../test/hftest/hftest.py) for details
on how this works.
## Other resources
When running tests under the FVP we also use a prebuilt version of TF-A, which
is checked in under
-[`prebuilts/linux-aarch64/arm-trusted-firmware/`](https://hafnium.googlesource.com/hafnium/prebuilts/+/refs/heads/master/linux-aarch64/arm-trusted-firmware/).
+[`prebuilts/linux-aarch64/arm-trusted-firmware/`](https://review.trustedfirmware.org/plugins/gitiles/hafnium/prebuilts/+/refs/heads/master/linux-aarch64/arm-trusted-firmware/).
The
-[README](https://hafnium.googlesource.com/hafnium/prebuilts/+/refs/heads/master/linux-aarch64/arm-trusted-firmware/README.md)
+[README](https://review.trustedfirmware.org/plugins/gitiles/hafnium/prebuilts/+/refs/heads/master/linux-aarch64/arm-trusted-firmware/README.md)
there has details on how it was built. The source code is available from the
-[Arm Trusted Firmware site](https://developer.trustedfirmware.org/dashboard/view/6/).
+[Arm Trusted Firmware site](https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git).
Documentation of the FVP (including memory maps) is
-[available from Arm](https://static.docs.arm.com/100966/1101/fast_models_fvp_rg_100966_1101_00_en.pdf).
+[available from Arm](https://developer.arm.com/docs/100966/latest).
diff --git a/docs/GettingStarted.md b/docs/GettingStarted.md
index 3cb2833..a1d53b7 100644
--- a/docs/GettingStarted.md
+++ b/docs/GettingStarted.md
@@ -5,7 +5,7 @@
## Getting the source code
```shell
-git clone --recurse-submodules https://hafnium.googlesource.com/hafnium && (cd hafnium && f=`git rev-parse --git-dir`/hooks/commit-msg ; curl -Lo $f https://gerrit-review.googlesource.com/tools/hooks/commit-msg ; chmod +x $f)
+git clone --recurse-submodules https://git.trustedfirmware.org/hafnium/hafnium.git && (cd hafnium && f=`git rev-parse --git-dir`/hooks/commit-msg ; curl -Lo $f https://review.trustedfirmware.org/tools/hooks/commit-msg ; chmod +x $f ; for m in `git rev-parse --git-dir`/modules/*; do cp $f $m/hooks/commit-msg; done)
```
To upload a commit for review:
@@ -14,8 +14,8 @@
git push origin HEAD:refs/for/master
```
-Browse source at https://hafnium.googlesource.com/hafnium. Review CLs at
-https://hafnium-review.googlesource.com/.
+Browse source at https://review.trustedfirmware.org/plugins/gitiles/. Review CLs
+at https://review.trustedfirmware.org/.
See details of [how to contribute](../CONTRIBUTING.md).
@@ -54,6 +54,7 @@
Next, you need to create a manifest which will describe the VM to Hafnium.
Follow the [Manifest](Manifest.md) instructions and build a DTB with:
+
```
/dts-v1/;
@@ -69,8 +70,8 @@
};
```
-Follow the [Hafnium RAM disk](HafniumRamDisk.md) instructions
-to create an initial RAM disk for Hafnium with Linux as the primary VM.
+Follow the [Hafnium RAM disk](HafniumRamDisk.md) instructions to create an
+initial RAM disk for Hafnium with Linux as the primary VM.
The following command line will run Hafnium, with the RAM disk just created,
which will then boot into the primary Linux VM: