| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
| |
This server allows the user to control the parameters of the state for
displaying the lights.
|
| |
|
|
| |
This helps by creating one location to add state parameters.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a mini shell to the tcp server that allows the user
to modify the current state.
Commands are in the form:
set [int_attribute] (=|+=|-=) [number]
set [bool_attribute] (on|off|toggle)
print
end
for example:
set brightness += 5
set power on
print
end
|
| |
|
|
|
|
|
|
| |
There is still definitely some jenk to it. For one I still
need to figure out how to protect critical sections to prevent stutter.
I do need to set up a timer to control the time incrementer rather than
depending on the speed of the spi bus.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Increases the nmuber of LEDs to the full 300 roll.
Can connect to the device using netcat. Set the color by entering
white
red
green
blue
yellow
teal
magenta
black
|
| | |
|
| | |
|
| |
|
|
| |
This adds a small subsystem to connect to a basic WPA accesspoint.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This driver can run lights! However it is very crude and does not
provide a great API. It does work though! Currently lights up 5 leds of
different colors.
Right now this does synchronous writes, which is not the best. It would
be better to be async, but I think that sholud not be a problem and will
shortly be done.
|
| |
|
|
|
| |
Got the SPI to work at 2.5 MHz. Just writes a bunch of 0xaf
to make the pattern easy to see on the oscilloscope.
|
|
|
Very basic, "Hello, World" infrastructure. For the most part, I did not
copy this from an existing example, rather, took inspiration from an
existing example. I want to avoid cargo-culting as much as possible.
|
