barebox.org/jsbarebox is now a HTTP 301 (Moved permanently) redirect to barebox.org/demo. Change all references we have to the old URL. Signed-off-by: Ahmad Fatoum <a.fatoum@xxxxxxxxxxxxxx> --- Documentation/boards/riscv.rst | 2 +- Documentation/devel/project-ideas.rst | 4 ++-- README.md | 2 +- test/riscv/tinyemu@rv64i_defconfig.yaml | 2 +- test/riscv/tinyemu@virt32_defconfig.yaml | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/boards/riscv.rst b/Documentation/boards/riscv.rst index 92f663cfb9e6..990bd16a640d 100644 --- a/Documentation/boards/riscv.rst +++ b/Documentation/boards/riscv.rst @@ -58,7 +58,7 @@ To activate add:: into the config file. -See https://barebox.org/jsbarebox/?graphic=1 for a live example. +See https://barebox.org/demo/?graphic=1 for a live example. BeagleV ------- diff --git a/Documentation/devel/project-ideas.rst b/Documentation/devel/project-ideas.rst index d9957e409178..da146c3e520e 100644 --- a/Documentation/devel/project-ideas.rst +++ b/Documentation/devel/project-ideas.rst @@ -185,13 +185,13 @@ barebox to a new board, for new users who are only interested in trying it out: The browser runs Tinyemu, a virtual machine in which barebox executes as if on real hardware and the user can manipulate the (virtual) hardware from the barebox shell and learn about barebox -conveniences: barebox.org/jsbarebox/ +conveniences: barebox.org/demo/ The project is about streamlining this demo: CPU usage currently is quite high and teaching barebox to idle the CPU (as we do on sandbox) didn't help. This needs to be analyzed with the profiling tools provided with modern browsers. The remainder of the project can then -focus on improving the jsbarebox tutorial. e.g. by adding new +focus on improving the tutorial inside the demo. e.g. by adding new peripherals to the virtual machine. Expected outcome is snappier and less CPU-intensive barebox demo. diff --git a/README.md b/README.md index a668f8aee224..acb4a28a8b16 100644 --- a/README.md +++ b/README.md @@ -6,7 +6,7 @@ that integrates DOOM with the available barebox frameworks for framebuffer, input, file system and so on ... etc. This allows it to run everywhere where barebox is running, be it on a x86 laptop under UEFI, on industrial machinery or even a RISC-V emulator compiled to WebAssembly. -Head over to [barebox.org](https://barebox.org/jsbarebox/?graphic=1) to try +Head over to [barebox.org](https://barebox.org/demo/?graphic=1) to try the latter out. As barebox often functions as bare metal hardware bring up kit, it can diff --git a/test/riscv/tinyemu@rv64i_defconfig.yaml b/test/riscv/tinyemu@rv64i_defconfig.yaml index e9624160ef0a..cb22afc68528 100644 --- a/test/riscv/tinyemu@rv64i_defconfig.yaml +++ b/test/riscv/tinyemu@rv64i_defconfig.yaml @@ -13,7 +13,7 @@ targets: - virtio-mmio runner: download: - bbl64.bin: https://barebox.org/jsbarebox/bbl64.bin + bbl64.bin: https://barebox.org/demo/bbl64.bin images: barebox-dt-2nd.img: !template "$LG_BUILDDIR/images/barebox-dt-2nd.img" tools: diff --git a/test/riscv/tinyemu@virt32_defconfig.yaml b/test/riscv/tinyemu@virt32_defconfig.yaml index 1102f36aca2b..bc6eada37684 100644 --- a/test/riscv/tinyemu@virt32_defconfig.yaml +++ b/test/riscv/tinyemu@virt32_defconfig.yaml @@ -13,7 +13,7 @@ targets: - virtio-mmio runner: download: - bbl32.bin: https://barebox.org/jsbarebox/bbl32.bin + bbl32.bin: https://barebox.org/demo/bbl32.bin images: barebox-dt-2nd.img: !template "$LG_BUILDDIR/images/barebox-dt-2nd.img" tools: -- 2.39.2
