New in this sub, some questions…

1. 3

   1 6 62 8.9 HolyC

   Discontinued templeos in userspace

   In my opinion the best hope is to provide the same user experience running on top of a well established kernel which already has all the drivers. Something similar to what I envisioned is being started here: https://github.com/nrootconauto/3Days

2. InfluxDB

   www.influxdata.com featured

   InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.

   

3. circle

   2 33 2,015 9.1 C

   A C++ bare metal environment for Raspberry Pi with USB (32 and 64 bit) (by rsta2)

   

   The only other reasonable option would be to port it to a new platform which is popular that has a few well documented hardware interfaces so as not to create a hellish nightmare writing drivers. Maybe then you could do a one-off port to that platform (though you might have to re-target the HolyC compiler to target it instead if it is not x86_64). The Raspberry PI seems like a decent option here since there is already a baremetal C++ library supporting USB, keyboard, mouse, sound, video, and as an added bonus UART, I2C, SPI, GPIO. You would have good code examples for porting all the necessary drivers. But obviously this would still be a lot of work and the compiler would need to be re-targeted and user space adapted for running on ARM. That being said backwards compatibility is strong, ARM seems actually interested in keeping it that way (at least for now). The library I'm talking about is here: https://github.com/rsta2/circle

Suggest a related project