move gentoo sffs page to different location

diff --git a/HDL_workflow/gentoo-sffs.mdwn b/HDL_workflow/gentoo-sffs.mdwn
deleted file mode 100644 (file)
index 27cbf10..0000000
--- a/HDL_workflow/gentoo-sffs.mdwn
+++ /dev/null
@@ -1,82 +0,0 @@
-# Tutorial for bootstrapping Gentoo with sffs compliance from source. 
-
-Useful Links (External):
-
-* [Read the Gentoo handbook thoroughly, it's all you need](https://wiki.gentoo.org/wiki/Handbook:PPC64)
-
-## Video Tutorial
-
-[todo](todo) 
-
-## Reasoning:
-
-Libre-SOC builds upon the OpenPOWER ISA v3.0 but does not include many parts of the architecture typically found on production silicon, like AltiVec, VSX, and 128-bit hardware floating point. Because of this, we need (at this time, might change in the future when glibc supports detecting VSX vs SVP64 etc) to rebuild the stage 3 system to not include any of those instructions, making it compliant with [sffs (slides 5 & 6)](https://ics2020.bsc.es/sites/default/files/uploaded/brian_thompto_ICS2020_SLIDES.pdf).
-
-To do this, you need to rebuild Gentoo from a known working stage3 archive, which we will guide you through.
-
-Do note that given the rolling release nature of Gentoo, it is almost impossible to get the same system with the specific package versions we have without using the same stage3 version we used.
-
-## System requirements
-
-- A POWER system that can run Debian Bookworm (meaning POWER8 and newer)
-- At least 80GB of hard disk space
-
-Cross compiling will make this process much more complicated and is generally not recommended.
-
-It is expected for you to use Debian for the host OS (anything else
-is unsupported: many contributors have repeatedly gotten into trouble by not following this advice)
-
-## Setting up Gentoo from stage3 and rebuilding (recommended method)
-
-You will need to run these commands:
-
-    $ curl -O [link to stage3]
-    # sudo bash
-    # mkdir gentoo-sffs && cd gentoo-sffs
-    # tar xpvf gentoo-sffs.tar.xz --xattrs-include='*.*' --numeric-owner
-    # cd ..
-
-Follow these steps from the Gentoo handbook:
-
-* [Copy DNS info](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Base#Copy_DNS_info)
-
-* [Mount necessary filesystems](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Base#Mounting_the_necessary_filesystems)
-
-* [Enter the chroot environment](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Base#Entering_the_new_environment)
-
-After which you need to add our build flags replacing the default ones in `/etc/portage/make.conf`
-
-`COMMON_FLAGS="-O2 -pipe -mcpu=power9 -mno-altivec -mno-vsx -mno-crypto -mno-htm -mlong-double-64"`
-
-`CPU_FLAGS_PPC=""`
-
-Finally, rebuild everything on the system:
-
-    # emerge -e --ask --keep-going @world
-
-# (Optional) Building an updated Gentoo SFFS
-
-This is highly not recommended unless you specifically want to explore how newer versions of software will behave when built with the SFFS flags.
-
-One way of doing this is to just set up Gentoo SFFS from the provided stage3, add out `make.conf` options and then upgrade everything, that is much simpler and easier to roll-back if need be.
-
-After having a working chroot using the stage3 as outlined earlier, run these commands in the chroot:
-
-    # emerge-webrsync
-    # emerge --ask --verbose --update --deep --newuse @world
-
-The other way is to create a new Gentoo chroot or virtual machine under POWER using the [handbook](https://wiki.gentoo.org/wiki/Handbook:PPC64), and once you reach the [stage3 tarball](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Stage#Unpacking_the_stage_tarball) step, download our [make.conf](link) and copy it to 
- `/etc/portage/make.conf`, replacing the provided one, and run:
-
-    # emerge -e --ask --keep-going @world
-    # emerge-webrsync
-    # emerge --ask --verbose --update --deep --newuse @world
-
-To first rebuild Gentoo for SFFS, and then update the repositories, and finally to upgrade the software you have.
-
-## Notes and issues
-
-* Gentoo's base system packages will not complain when building for SFFS (as of July 2023, can change depending on updates)
-* The Linux kernel cannot boot without AltiVec and VSX, even though they are build-time options. The solution for now is to use [microwatt's 5.7 kernel](https://lore.kernel.org/all/CAPweEDw710zFK8KLZY5gsQxEkQKrDiFkNRgABY9HJZ1rxpeVCg@mail.gmail.com/T/) and to incorporate the needed patches upstream in the future.
-* Previous note also means this is purely a chroot environment, this page will be updated once it becomes possible to boot a full VM of this build.
-* glibc *may* have some issues on sffs, the only way to test this is to run on microwatt which will be done soon.

diff --git a/SFFS/gentoo_bootstrap.mdwn b/SFFS/gentoo_bootstrap.mdwn
new file mode 100644 (file)
index 0000000..27cbf10
--- /dev/null
+++ b/SFFS/gentoo_bootstrap.mdwn
@@ -0,0 +1,82 @@
+# Tutorial for bootstrapping Gentoo with sffs compliance from source. 
+
+Useful Links (External):
+
+* [Read the Gentoo handbook thoroughly, it's all you need](https://wiki.gentoo.org/wiki/Handbook:PPC64)
+
+## Video Tutorial
+
+[todo](todo) 
+
+## Reasoning:
+
+Libre-SOC builds upon the OpenPOWER ISA v3.0 but does not include many parts of the architecture typically found on production silicon, like AltiVec, VSX, and 128-bit hardware floating point. Because of this, we need (at this time, might change in the future when glibc supports detecting VSX vs SVP64 etc) to rebuild the stage 3 system to not include any of those instructions, making it compliant with [sffs (slides 5 & 6)](https://ics2020.bsc.es/sites/default/files/uploaded/brian_thompto_ICS2020_SLIDES.pdf).
+
+To do this, you need to rebuild Gentoo from a known working stage3 archive, which we will guide you through.
+
+Do note that given the rolling release nature of Gentoo, it is almost impossible to get the same system with the specific package versions we have without using the same stage3 version we used.
+
+## System requirements
+
+- A POWER system that can run Debian Bookworm (meaning POWER8 and newer)
+- At least 80GB of hard disk space
+
+Cross compiling will make this process much more complicated and is generally not recommended.
+
+It is expected for you to use Debian for the host OS (anything else
+is unsupported: many contributors have repeatedly gotten into trouble by not following this advice)
+
+## Setting up Gentoo from stage3 and rebuilding (recommended method)
+
+You will need to run these commands:
+
+    $ curl -O [link to stage3]
+    # sudo bash
+    # mkdir gentoo-sffs && cd gentoo-sffs
+    # tar xpvf gentoo-sffs.tar.xz --xattrs-include='*.*' --numeric-owner
+    # cd ..
+
+Follow these steps from the Gentoo handbook:
+
+* [Copy DNS info](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Base#Copy_DNS_info)
+
+* [Mount necessary filesystems](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Base#Mounting_the_necessary_filesystems)
+
+* [Enter the chroot environment](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Base#Entering_the_new_environment)
+
+After which you need to add our build flags replacing the default ones in `/etc/portage/make.conf`
+
+`COMMON_FLAGS="-O2 -pipe -mcpu=power9 -mno-altivec -mno-vsx -mno-crypto -mno-htm -mlong-double-64"`
+
+`CPU_FLAGS_PPC=""`
+
+Finally, rebuild everything on the system:
+
+    # emerge -e --ask --keep-going @world
+
+# (Optional) Building an updated Gentoo SFFS
+
+This is highly not recommended unless you specifically want to explore how newer versions of software will behave when built with the SFFS flags.
+
+One way of doing this is to just set up Gentoo SFFS from the provided stage3, add out `make.conf` options and then upgrade everything, that is much simpler and easier to roll-back if need be.
+
+After having a working chroot using the stage3 as outlined earlier, run these commands in the chroot:
+
+    # emerge-webrsync
+    # emerge --ask --verbose --update --deep --newuse @world
+
+The other way is to create a new Gentoo chroot or virtual machine under POWER using the [handbook](https://wiki.gentoo.org/wiki/Handbook:PPC64), and once you reach the [stage3 tarball](https://wiki.gentoo.org/wiki/Handbook:PPC64/Installation/Stage#Unpacking_the_stage_tarball) step, download our [make.conf](link) and copy it to 
+ `/etc/portage/make.conf`, replacing the provided one, and run:
+
+    # emerge -e --ask --keep-going @world
+    # emerge-webrsync
+    # emerge --ask --verbose --update --deep --newuse @world
+
+To first rebuild Gentoo for SFFS, and then update the repositories, and finally to upgrade the software you have.
+
+## Notes and issues
+
+* Gentoo's base system packages will not complain when building for SFFS (as of July 2023, can change depending on updates)
+* The Linux kernel cannot boot without AltiVec and VSX, even though they are build-time options. The solution for now is to use [microwatt's 5.7 kernel](https://lore.kernel.org/all/CAPweEDw710zFK8KLZY5gsQxEkQKrDiFkNRgABY9HJZ1rxpeVCg@mail.gmail.com/T/) and to incorporate the needed patches upstream in the future.
+* Previous note also means this is purely a chroot environment, this page will be updated once it becomes possible to boot a full VM of this build.
+* glibc *may* have some issues on sffs, the only way to test this is to run on microwatt which will be done soon.