@ -1,14 +1,10 @@
# Kaleidoscope-EEPROM-Settings
# Kaleidoscope-EEPROM-Settings
![status][st:experimental] [![Build Status][travis:image]][travis:status]
[![Build Status][travis:image]][travis:status]
[travis:image]: https://travis-ci.org/keyboardio/Kaleidoscope-EEPROM-Settings.svg?branch=master
[travis:image]: https://travis-ci.org/keyboardio/Kaleidoscope-EEPROM-Settings.svg?branch=master
[travis:status]: https://travis-ci.org/keyboardio/Kaleidoscope-EEPROM-Settings
[travis:status]: https://travis-ci.org/keyboardio/Kaleidoscope-EEPROM-Settings
[st:stable]: https://img.shields.io/badge/stable-✔-black.svg?style=flat& colorA=44cc11& colorB=494e52
[st:broken]: https://img.shields.io/badge/broken-X-black.svg?style=flat& colorA=e05d44& colorB=494e52
[st:experimental]: https://img.shields.io/badge/experimental----black.svg?style=flat& colorA=dfb317& colorB=494e52
To be able to reliably store persistent configuration in `EEPROM` , we need to be
To be able to reliably store persistent configuration in `EEPROM` , we need to be
able to split up the available space for plugins to use. We also want to make
able to split up the available space for plugins to use. We also want to make
sure that we notice when the `EEPROM` contents and the firmware are out of sync.
sure that we notice when the `EEPROM` contents and the firmware are out of sync.