amy/upiwin
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
UPIWIN: Micro Pi Windows Kernel
167 Commits 2 Branches 1 Tag 7.2 MiB
C 88.7%
Python 8.4%
Makefile 2.9%
master
Go to file
Amy G. Bowersox ea7bdde05d One more disclaimer on the front end of the CoC 
If you copy it, you can modify the "Owner" only.
2020-03-02 10:06:28 -07:00
buildutils The code has to be GPL'd, because the license of the BCM2835 library requires 2019-12-12 09:24:58 -07:00
docs/templates The code has to be GPL'd, because the license of the BCM2835 library requires 2019-12-12 09:24:58 -07:00
resources add the undo and clear commands with their icons 2019-12-11 15:52:49 -07:00
scripts The code has to be GPL'd, because the license of the BCM2835 library requires 2019-12-12 09:24:58 -07:00
src The code has to be GPL'd, because the license of the BCM2835 library requires 2019-12-12 09:24:58 -07:00
.gitignore fixed up the makefile and the symbol references in fbinit.c 2019-12-06 20:51:41 -07:00
CODE-OF-CONDUCT.md One more disclaimer on the front end of the CoC 2020-03-02 10:06:28 -07:00
LICENSE.md The code has to be GPL'd, because the license of the BCM2835 library requires 2019-12-12 09:24:58 -07:00
Makefile The code has to be GPL'd, because the license of the BCM2835 library requires 2019-12-12 09:24:58 -07:00
README.md bump the version number (actually establish it for the first time!) 2019-12-12 13:58:16 -07:00

README.md

UPIWIN - Micro Pi Windows Kernel

Release 0.1 - December 12, 2019

This project involves the development of a framework for running self-contained applications in Python on a Raspberry Pi with LCD graphical output and touchscreen input. The ultimate goal is to produce a framework which is flexible enough to serve any number of “appliance” needs, by using different Python scripts over the same native-code substrate, deployed on an inexpensive embedded platform.

Hardware requirements

  • Raspberry Pi 3 with PiTFT touchscreen (Adafruit product ID 2423)

Acknowledgements

A good portion of this code was written during the VMware Carbon Black Hackathon 3.3, December 6-13 2019. Grateful acknowledgement is provided to VMware Carbon Black for the time to accomplish this coding.