(no commit message)

[libreriscv.git] / shakti / m_class / libre_3d_gpu.mdwn

diff --git a/shakti/m_class/libre_3d_gpu.mdwn b/shakti/m_class/libre_3d_gpu.mdwn
index 5d1f5d274d4b759736d34c1a5aaa71c731cc99c8..2116ba3d088a38601561b77064b944eec0e1c0bc 100644 (file)
--- a/shakti/m_class/libre_3d_gpu.mdwn
+++ b/shakti/m_class/libre_3d_gpu.mdwn
@@ -106,9 +106,9 @@ As I mention in the above page, one of the problems with doing a completely sepa
 
 Will that approach work? Honestly I have absolutely no idea, but it would be a fascinating and extremely ambitious research project.
 
-Can we get people to fund it?  Yeah I do.  there's a lot of buzz about RISC-V, and a lot of buzz can be created about a libre 3D GPU. If that same GPU happens to be good at doing crypto-currency mining there will be a LOT more attention paid, particularly given that people have noticed that relying on proprietary GPUs and CPUs to manage billions of dollars worth of crypto-currency, when the NSA is *known* to have blackmailed intel into putting a spying back-door co-processor in to x86, and that it miiight not be a good idea to trust proprietary hardware
+Can we get people to fund it?  Yeah I do.  there's a lot of buzz about RISC-V, and a lot of buzz can be created about a libre 3D GPU. If that same GPU happens to be good at doing crypto-currency mining there will be a LOT more attention paid, particularly given that people have noticed that relying on proprietary GPUs and CPUs to manage billions of dollars worth of crypto-currency, when the NSA is *known* to have blackmailed intel into putting a spying back-door co-processor in to x86, and that it miiight not be a good idea to trust proprietary hardware:
 
-<libreboot.org/faq#intelme>
+<http://libreboot.org/faq#intelme>
 
 ## Q & A