From 7fd00bd791c57eb058b404f33c5caa87f3ce44fe Mon Sep 17 00:00:00 2001 From: Greg Sadetsky Date: Mon, 4 Jul 2022 17:57:19 -0400 Subject: [PATCH] fix 404 link --- src/common/pico_scanvideo/README.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/common/pico_scanvideo/README.adoc b/src/common/pico_scanvideo/README.adoc index 2a6af1d..930d507 100644 --- a/src/common/pico_scanvideo/README.adoc +++ b/src/common/pico_scanvideo/README.adoc @@ -6,7 +6,7 @@ pixels at this rate under program control, which is great because (given that th Actual framebuffers are not required (though can be used for modes that aren't too high resolution - 256K isn't a huge amount for a framebuffer), and because content is generated in time with the "beam", no double buffering is required. -This library is _deliberately_ very low level, but gives you full control over everything. In the future we will likely add more convenience APIs for dealing with some common framebuffer formats. Note the https://github.com/raspberrypi/pico-playground/scanvideo/mandelbrot[mandelbrot] example actually does use a frame buffer that is taken care of by an IRQ handler leaving both cores for user work, if you want to look at that. +This library is _deliberately_ very low level, but gives you full control over everything. In the future we will likely add more convenience APIs for dealing with some common framebuffer formats. Note the https://github.com/raspberrypi/pico-playground/tree/master/scanvideo/mandelbrot[mandelbrot] example actually does use a frame buffer that is taken care of by an IRQ handler leaving both cores for user work, if you want to look at that. == Types of display