XO Laptop On Its Way

While high on Vicodin after my knee surgery, I disobeyed the post-surgery advice that said not to make any big decisions and I purchased an XO Laptop through the Give One Get One program. I really should have written about this sooner, because now it's too late for me to talk anyone else into doing it with me. The program ended December 31st. I think I was feeling a bit guilty about spending the money, especially while under a pain-killer induced haze. I'm not usually that irresponsible! The more I learn about the laptop, though, the more the guilt is replaced with excitement. This is one freaking cool computer. The video of Ivan Krstic impressed me the most. Custom ASICs, extreme power management, and serious security (and he's from Croatia, where I lived for two years. Bok, Ivan!), what more could a geek want?

Because I didn't order at the beginning of the G1G1 program I knew my laptop wouldn't be arriving in time for Christmas, but I was hoping maybe it'd come in time for my birthday (which is the day after Christmas...). Now that's it's almost January, the suspense is killing me, when will it arrive? I searched around a bit and found this great bit of advice, and called FedEx today. My package from Brightstar is scheduled to arrive this week (they actually told me which day, but in case you are planning on hiding in the bushes at my house and intercepting it, I'm not telling)! Now I'm really excited. I have to keep reminding myself to tone down my expectations a little. It is geared for kids and education, not movie watching and game playing, after all. I figure that as long as I can read my email with it on a road trip, it'll be worthwhile. I'll feel warm and fuzzy about the child in Cambodia (or wherever) who gets one too.

Comments

Post a Comment

Popular posts from this blog

SystemVerilog Fork Disable "Gotchas"

This is a long post with a lot of SystemVerilog code. The purpose of this entry is to hopefully save you from beating your head against the wall trying to figure out some of the subtleties of SystemVerilog processes (basically, threads). Subtleties like these are commonly referred to in the industry as "Gotchas" which makes them sound so playful and fun, but they really aren't either. I encourage you to run these examples with your simulator (if you have access to one) so that a) you can see the results first hand and better internalize what's going on, and b) you can tell me in the comments if this code works fine for you and I'll know I should go complain to my simulator vendor. OK, I'll start with a warm-up that everyone who writes any Verilog or SystemVerilog at all should be aware of, tasks are static by default. If you do this: module top; task do_stuff ( int wait_time); #wait_time $display ( "waited %0d, then did stuff" , wa
Read more

'git revert' Is Not Equivalent To 'svn revert'

I just learned that if you have some changes in your working tree that you want to get rid of, you don't type 'git revert' like you might guess. No, that's what cvs, subversion, mercurial, and bazaar (to name a few) use revert to mean, but not git. With git, revert is used to undo actual commits. Thankfully, you can undo your revert with another 'git revert', I just learned. So let me repeat to be clear, if you have changes to your working files that you want to abandon, DO NOT do this: git revert HEAD That will undo your last commit. Do this instead: git reset --hard HEAD I'm glad I have that straightened out now. I'm wondering if /etc was really a good place for me to start out playing with git. UPDATE: Nearly two years later and I'm still getting comments on this. I'm glad I've been able to help people out this way. The discussion in the comments is good, and one thing I'd like to point out is that I now always use
Read more

Git Rebase Explained

Image
Introduction Rebase is a helpful git command that can be used to turn a branchy two-headed version history into an easy to follow linear one. A linear history is much easier for a human eye to follow and a human brain to understand. Rebase is a very safe command to use, despite some fear that people have about it. This post should explain how rebase works and clear up any misunderstandings about it. Rebase Basics The short summary of rebase is that it cuts commits out of the git history and reconnects them somewhere else. Let's say the common scenario comes up: you commit a change to the main branch of a repository, you then run  git fetch , and in come a couple changes that other people made on the main branch. If your commit is version 46f and the others that just came in on the fetch are versions ef9 and 4a2, your version history might look like this: The main branch now has two heads, 46f and 4a2. You can run  git rebase  to disconnect your commit from version d88 and connect i
Read more