Thought experiments

-


For someone of physics background... this news is interesting:



http://www.wired.com/science/discoveries/magazine/15-06/st_best

Future vehicles: http://www.wired.com/cars/futuretransport/news/2007/06/future_engines

Comments

Post a Comment

Popular posts from this blog

beagleboard recovery take 2

-
[2013-03-06 update]: after a few years of letting things rot, I just managed to pick up my old binaries and gave it a dry run: https://github.com/nmenon/beagle-recover  has the original working binaries since the google groups link no longer work. NOTE: I HAVE NOT TRIED WITH ANY OF THE LATEST SOURCES. I do not have plans to do so in the future as well  - an quick try indicated things are broke :( [Original post] http://groups.google.com/group/beagleboard/web/beagle_recover.tar.bz2 has the recovery package ready to go for ubuntu 8.04 32bit OS: download this, run sudo ./recover_beagle.sh - as shown in the video... Steps summary: 1. first shutdown the board. 2. run 'sudo recover_beagle.sh /dev/ttyUSB0' in a terminal -> you need super user permissions(sudo permissions) to run this script. 3. Keep the pushbutton S1pressed while powering on the board -> there are two white push button switches, use the one closer to the edge of the board NOTE: if your nand is com...
Read more

Quick and Dirty userspace testing of regulator with virtual consumer

-
Writing a driver for a new regulator is usually fun, until you need to test the darned thing. Many of the users of the regulator is probably not yet ready in an development environment and need to test cant wait. I had recently a similar situation and found CONFIG_REGULATOR_VIRTUAL_CONSUMER You'd probably register and provide and regulator supply, but without a driver using it in a controlled environment (read shell script or so), it is hard to poke holes completely into your driver. Steps are rather simple. Assumption - you already have a regulator registered in the system and you are aware of the regulator name - You can also figure out it's name by the following (an example from 3.9-rc8 on Beagle-XM): # head /sys/class/regulator/*/name ==> /sys/class/regulator/regulator.0/name /sys/class/regulator/regulator.1/name /sys/class/regulator/regulator.2/name /sys/class/regulator/regulator.3/name /sys/class/regulator/regulator.4/name /sys/class/regulator/regulator.5/...
Read more

Setting up Email forwarding System for GIT

-
Image
The post is a derivative of the omapzoom wiki page . Disclaimer: my mastery of the wiki tags are dismal.. apologies... some day i hope to have time to post it here Many new developers have been stumped when they need to use git-send-email in corporate environment – usually, if not as a norm, ms exchange servers form the backbone of such an email server system. This page was written based on one of such requirements. To get started, we shall consider common scenarios: a) Setting up a mail forwarding system with postfix on ubuntu b) Setting up a mail forwarding system on a fedora machine c) Using msmtp for using gmail a. to send a patch using a gmail ID b. to send a patch using your corporate ID but through gmail Postfix on Ubuntu – mail forwarding For setting up postfix, you need: a) A mail relay server which will allow your machine to talk to it -> speak to your IT representatives/ other developers sitting next to you b) Super user privileges on the machine you are working on. Step...
Read more