<drool>I was hoping to do something like this but have not done anything about it.</drool>
Affirmative on both. I believe I have an older Linksys minus a 5V supply (yes it is 5V and not 9V like everyone elses). I have a solder station that I could bring for those that don't have one. With regards to a microprocessor workshop anything is good but I have an application for serial data in and wireless network communication out. Anything is always a good start. Whoohoo!!! ----- Original Message ----- From: "Mark Carlson" <[EMAIL PROTECTED]> To: "CLUG General" <[email protected]> Sent: Friday, September 7, 2007 10:01:28 AM (GMT-0700) America/Denver Subject: [clug-talk] Two (hardware related) workshop ideas. Hello all, I was wondering if anyone would be interested in attending a workshop in either of the following areas: 1. WRT54GL hacking. I'm thinking, flash it with Linux, solder on some wires, and then write code to use any extra I/O in some fashion... It will probably cost around $70 to buy a 54GL unless you already have something similar already (and don't mind doing a little prep. work yourself) 2. Microcontrollers. There are some incredibly cheap microcontrollers out there right now (everything you need to start playing around for only $20! or even free sometimes!) I know the TI eZ430 MCUs +programmers can be obtained for $20 sometimes. We could do Zilog MCUs starting at $50~$100, or anything else we could come to a consensus on (ha!) As for dates, I'm thinking WRT hacking would be the end of october, and microcontrollers would be sometime early next year. Any takers? -Mark C P.S. I hate robots :-P _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
