Test upstream rev2

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,46 @@
+Thank you for opening an issue on an Adafruit Arduino library repository.  To
+improve the speed of resolution please review the following guidelines and
+common troubleshooting steps below before creating the issue:
+
+- **Do not use GitHub issues for troubleshooting projects and issues.**  Instead use
+  the forums at http://forums.adafruit.com to ask questions and troubleshoot why
+  something isn't working as expected.  In many cases the problem is a common issue
+  that you will more quickly receive help from the forum community.  GitHub issues
+  are meant for known defects in the code.  If you don't know if there is a defect
+  in the code then start with troubleshooting on the forum first.
+
+- **If following a tutorial or guide be sure you didn't miss a step.** Carefully
+  check all of the steps and commands to run have been followed.  Consult the
+  forum if you're unsure or have questions about steps in a guide/tutorial.
+
+- **For Arduino projects check these very common issues to ensure they don't apply**:
+
+  - For uploading sketches or communicating with the board make sure you're using
+    a **USB data cable** and **not** a **USB charge-only cable**.  It is sometimes
+    very hard to tell the difference between a data and charge cable!  Try using the
+    cable with other devices or swapping to another cable to confirm it is not
+    the problem.
+
+  - **Be sure you are supplying adequate power to the board.**  Check the specs of
+    your board and plug in an external power supply.  In many cases just
+    plugging a board into your computer is not enough to power it and other
+    peripherals.
+
+  - **Double check all soldering joints and connections.**  Flakey connections
+    cause many mysterious problems.  See the [guide to excellent soldering](https://learn.adafruit.com/adafruit-guide-excellent-soldering/tools) for examples of good solder joints.
+
+  - **Ensure you are using an official Arduino or Adafruit board.** We can't
+    guarantee a clone board will have the same functionality and work as expected
+    with this code and don't support them.
+
+If you're sure this issue is a defect in the code and checked the steps above
+please fill in the following fields to provide enough troubleshooting information.
+You may delete the guideline and text above to just leave the following details:
+
+- Arduino board:  **INSERT ARDUINO BOARD NAME/TYPE HERE**
+
+- Arduino IDE version (found in Arduino -> About Arduino menu):  **INSERT ARDUINO
+  VERSION HERE**
+
+- List the steps to reproduce the problem below (if possible attach a sketch or
+  copy the sketch code in too): **LIST REPRO STEPS BELOW**

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,26 @@
+Thank you for creating a pull request to contribute to Adafruit's GitHub code!
+Before you open the request please review the following guidelines and tips to
+help it be more easily integrated:
+
+- **Describe the scope of your change--i.e. what the change does and what parts
+  of the code were modified.**  This will help us understand any risks of integrating
+  the code.
+
+- **Describe any known limitations with your change.**  For example if the change
+  doesn't apply to a supported platform of the library please mention it.
+
+- **Please run any tests or examples that can exercise your modified code.**  We
+  strive to not break users of the code and running tests/examples helps with this
+  process.
+
+Thank you again for contributing!  We will try to test and integrate the change
+as soon as we can, but be aware we have many GitHub repositories to manage and
+can't immediately respond to every request.  There is no need to bump or check in
+on a pull request (it will clutter the discussion of the request).
+
+Also don't be worried if the request is closed or not integrated--sometimes the
+priorities of Adafruit's GitHub code (education, ease of use) might not match the
+priorities of the pull request.  Don't fret, the open source community thrives on
+forks and GitHub makes it easy to keep your changes in a forked repo.
+
+After reviewing the guidelines above you can delete this text from the pull request.

.github/workflows/githubci.yml

@@ -0,0 +1,32 @@
+name: Arduino Library CI
+
+on: [pull_request, push]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: actions/setup-python@v4
+      with:
+        python-version: '3.x'
+    - uses: actions/checkout@v3
+    - uses: actions/checkout@v3
+      with:
+         repository: adafruit/ci-arduino
+         path: ci
+
+    - name: pre-install
+      run: bash ci/actions_install.sh
+
+    - name: test platforms
+      run: python3 ci/build_platform.py pico_rp2040
+
+#    - name: clang
+#      run: python3 ci/run-clang-format.py -e "ci/*" -e "bin/*" -r . 
+
+    - name: doxygen
+      env:
+        GH_REPO_TOKEN: ${{ secrets.GH_REPO_TOKEN }}
+        PRETTYNAME : "PicoDVI - Adafruit Fork"
+      run: bash ci/doxy_gen_and_deploy.sh

.gitignore

@@ -1,2 +1,5 @@
+Doxyfile*
+doxygen_sqlite3.db
+html
 .vscode
 build

Readme.md

@@ -1,6 +1,48 @@
+Special Fork of PicoDVI for RP2040/RP2350 Arduino Philhower Core + Adafruit_GFX
+========================================================================
+
+Implements a few framebuffer types to which Adafruit_GFX drawing operations
+can be made; not every permutation PicoDVI is capable of, but a useful subset.
+
+WARNING: all video modes require overclocking (performed automatically at
+run-time, nothing to select), occasionally over-volting (optionally selected
+in sketch code), and higher resolutions may require reducing the QSPI clock
+rate (Tools menu in future arduino-pico release). The RP2040 microcontroller
+is being run WAY beyond spec and there is a VERY SMALL BUT NONZERO
+POSSIBILITY OF PERMANENT DAMAGE. Please see LICENSE file; usual software
+disclaimers about liability apply, user accepts risk.
+
+Requires Earle Philhower III RP2040 Arduino core (not the "official" Arduino
+RP2040 core).
+
+Changes vs main PicoDVI repo:
+- Add library.properties file, src and examples directories per Arduino
+requirements.
+- A full copy of software/libdvi is made in src (originally was soft-linked but Arduino Library Manager does not approve). If any updates are made in the original PicoDVI libdvi directory, copy them here!
+- The file dvi_serialiser.pio.h, normally not part of the distribution and
+generated during the Pico SDK build process, is provided here for Arduino
+build to work. If any changes are made in dvi_serialiser.pio (either here
+or by bringing in updates from upstream code), this header will need to be
+regenerated.
+- extern "C" around most function defs, to be linkable with C++ (Arduino).
+- A couple compile-time constants have been changed to run-time configurable
+because some color and resolution things aren't known until a constructor is
+called: dvi_vertical_repeat and dvi_monochrome_tmds.
+- DVI_1BPP_BIT_REVERSE is switched '1' by default (to work with bit order
+used by GFXcanvas1 object). Pico SDK-built examples using 1-bit mode are
+fixed by changing the corresponding CMakeLists.txt files to set this to 0.
+Font data has had bit order reversed to match this layout.
+
+All files from the PicoDVI repo are kept even if not used in this build
+(e.g. apps and assets directories, among others) so same repo can still be
+used via Pico SDK if desired.
+
+Original Readme content:
+
 Bitbanged DVI on the RP2040 Microcontroller
 ===========================================
 
+
 ![](img/mountains.jpg)
 
 *640x480 RGB565 image, 640x480p 60 Hz DVI mode. 264 kB SRAM, 2x Cortex-M0+, system clock 252 MHz*