Although it has been a bit quiet here lately, this does not mean that I have not made progress. As the first in a upcoming series of reports, let me talk a bit about the problem of finding a remote control for my EPIA system. You might wonder why I need a remote control, considering what I’ve explained so far what the EPIA is supposed to do. Continue reading “A truely universal remote control for my EPIA system”
In a recent post I mentioned that the Linux kernel has a dedicated API for LEDs. This API is composed of the drivers/leds/ directory and the additional <linux/leds.h> include file, Documentation exists in form of the Documentation/leds-class.txt file. To quote:
“The underlying design philosophy is simplicity. LEDs are simple devices and the aim is to keep a small amount of code giving as much functionality as possible. Please keep this in mind when suggesting enhancements.”
While this goal appears supportable, the result leaves room for discussion. Continue reading “The shortcomings of the Linux LEDs API”
While analyzing hostapd and trying to find out where to hook in after WPA pairwise key exchange has completed, the need arose to get a gdb running on the target platform (the EPIA MII), so I could break in the function and obtain a backtrace.
In the course of my little EPIA MII project, I have to interface four custom LEDs which I connected to the MII’s internal parallel port connector. The LEDs are tri-state LEDs, that is, they can not be just turned on or off but can show three different colors, hence the name tri-state LEDs. The particular ones I bought can be either off or light in either green, orange or yellow. Naturally, green would be a good choice to indicate a “ready/everything’s right” condition, orange could indicate ongoing activity und yellow is a good candidate in case of errors. Each LED requires two pins plus a Ground connection, thus the eight data lines on the parallel port can drive four LEDs just fine.
Due to its connectivity options (Ethernet onboard, WLAN addable via PCI card, CardBus slot or USB for UMTS adapter, possibly even a CompactFlash adapter) the EPIA MII suggests itself, of course, as a router device and that’s what it was originally intended for. However, now in the first place it’ll have a slightly different assignment.
I recently mentioned my EPIA MII-based system. The EPIA MII is a highly integrated mainboard from Via’s Embedded division that comes in the itsy-tiny Mini-ITX form factor. I originally bought it way back together with a Casetronic Travla C158 case to be the base for an OpenWrt-based UMTS router. However I never got around it to it.
Now recently I rediscovered the hardware and started playing around with it again. But before I go into details about my plans with the system, here’s some pictures first: