| At line 22 changed one line |
| The question is then to locate the relevant Linux version and hope that it works well enough: |
| The question is then to locate the relevant Linux version and hope that it works well enough. |
| At line 24 changed one line |
| * OpenWrt, DD-Wrt to handle WRT routers, WD Netcenter and a host of small NAS and routers. |
| * [OpenWrt|http://openwrt.org], [DD-Wrt|http://www.dd-wrt.com/site/index] to handle WRT routers, WD Netcenter and a host of small NAS and routers. |
| * [Android] which is Linux-based |
| * see also [Linux for gadgets] |
| * see also [Alternative Firmwares] |
| At line 29 added 10 lines |
| |
| !! Modern stacks |
| It's important to consider new gadgets too. If we can target the new gadgets every time we target an old one it makes it more worthwhile to work on the old gadget. |
| New gadgets often offer: |
| * HTML5/javascript |
| * Java |
| * Linux |
| * iOS (C++/Objective C on Unix-like with proprietary APIs) |
| * Flash/Flash Lite |
| * .Net/C# |
| At line 40 added 4 lines |
| !! Shorting the stack |
| Another possibility is to avoid running software on the reused gadget as much as possible. |
| For instance, we can use the device as a [dumb terminal|Remote terminal solutions] and run the software on another machine. |
| Or the gadget may have existing software that lets it share its devices (SMB fileserver, export USB over Ethernet, web service to collect sensor values etc.) |
| At line 45 added one line |
| !!! Reuse strategies |
| At line 47 added 24 lines |
| !! Classic and simple |
| ! Hand-me-down |
| A classic way to find new uses for an old gadget is to find somebody who does not need or can't have the new gadget and set them up with the old one. This might require installing some new software (e.g. a drawing program on a Palm so that a kid is happy with it)\ |
|
| !! DIY |
| One can get parts out of an old gadget or build a system using it. |
|
| Old gadgets can be part of a DIY [projects|Gadget Oriented projects]. To help with that, a database of projects and a database of gadgets can be useful to help match old gadgets with projects. |
|
| |
| !! Planning ahead |
| When buying new gadgets we have the opportunity to prepare for future reuse. |
| Here are criteria of reuse that should be optimized |
| * connectivity: buy hardware with more connectivity options (USB slave/host, bluetooth, wifi etc.) |
| * software: buy hardware with Linux support or a native stack that is open |
| * features: buy hardware with interesting features (camera, thermometer, barometer, GPS etc.) |
| * maintenance: buy hardware where parts can be replaced (e.g. battery) |
| * ruggedness: buy hardware that is more susceptible to resist a long time (e.g. Gorilla glass for screen, fewer parts etc.) |
| * popularity: target devices that are popular, especially popular among geeks. That way a wealth of hacks and parts should be available when you start repurposing the gadget. |
| Let's try to [assess a couple gadgets|Gadget evaluation sheet 1] |
|
|
|
|