Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update roadmap.md #2329

Merged
merged 3 commits into from
Jul 11, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 6 additions & 35 deletions Documentation/roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,43 +6,14 @@ Our goal is to create a set of world-class APIs and tooling that will support a

The following deliverables are not in any particular order:

* [ ] Add bindings for more devices
* [ ] Add/Test support on more boards
* [ ] Onboard more customers and work on making them successful
* [ ] Improve the Eventing APIs for the SysFS driver for GPIO (#378)
* [ ] Add infrastructure required for servicing bindings package
* [ ] Improve documentation for onboarding, adding device bindings, working with samples
* Add bindings for more devices
* Add/Test support on more boards
* [ ] Improve documentation for onboarding, adding device bindings, working with samples (https://github.com/dotnet/iot/issues/2261)
pgrawehr marked this conversation as resolved.
Show resolved Hide resolved
* [ ] Improve the abstraction for devices in Iot.Device.Bindings package
* [ ] Collaborate with IoT Plug and Play
* [ ] Add E2E sample that leverages Azure IoT Hub to showcase the integration with Azure services
* [ ] Add testing for I2C, SPI, PWM protocols
* [ ] Add testing infrastructure for Iot.Device.Bindings
* [ ] Add control engineering algorithms (for example: PID)
* [ ] Add E2E sample that leverages the integration with Azure services
* [ ] Improve testing setup - i.e. distributed ways to contribute to queue (i.e. @Ellerbach shares RPi3 + encoder and @krwq shares RPi3 + SenseHat)
* [ ] Support new protocols; for example I2S.
* [ ] Support common serial protocols: RS-485 Serial Port, Modbus, 1-wire
* [ ] Publish Docker images for a subset of samples

## Completed deliverables for our 3.0 release

* Support General-purpose input/output protocols: GPIO, SPI, I2C, and PWM
* Support analog-to-digital protocols: ADC
* Support CAN bus
* Support Raspberry Pi 3 on Linux and Windows 10 IoT Core RS5
* Support Hummingboard Edge on Linux and Windows 10 IoT Core RS5
* Support BeagleBoard Black on Linux and Windows 10 IoT Core RS5
* Support sysfs (/sys/class/gpio) for Generic/Portable Device Driver on Linux Kernel 3.6+
* Support libgpiod (/dev/gpiochipX) for Generic/Portable Device Driver on Linux Kernel 4.8+
* Stabilize System.Device.Gpio API
* Publish [System.Device.Gpio to NuGet.org](https://www.nuget.org/packages/System.Device.Gpio)
* Provide example dockerfiles for some samples
* Support x64
* Support ARM32
* Support ARM64
* Support Device Bindings for common sensors and microcontrollers such as those bundled with the [Microsoft IoT Starter Pack](https://www.adafruit.com/product/2733)
* Support Device Bindings and Canvas Widgets for LCDS, multi-panel [LED matrices](https://www.adafruit.com/product/607), and Displays
* Support Device Bindings for servo and stepper motors, motor controllers
* Stabilize Iot.Device.Bindings APIs for Device Bindings
* Publish [Iot.Device.Bindings to NuGet.org](https://www.nuget.org/packages/Iot.Device.Bindings)
* [ ] Support common serial protocols: RS-485 Serial Port, Modbus

![dotnet iot rodmap](images/DotNetIotRoadmapComponents.png)

Expand Down
Loading