Archive for August, 2006

Toorcon 2006

Thursday, August 31st, 2006

I’m going to be doing a workshop this year at Toorcon 2006. The talk is a hardware hacking workshop that uses “secret-bunnie-hardware” as its subject. You might be able to guess what this hardware could be, given the other blog entries around this one. It may be the only opportunity to acquire one of these pieces of hardware until a few months from now. And yes, you have to pay Toorcon a fee to attend the workshop.

The talk is geared toward people with a good sense of Linux OS fundamentals and C coding experience, but little or no familiarity with hardware. I will teach you how to add sensors and write drivers for them, and also cover a few methods for extracting and modifying embedded firmwares. The size of the session is small so I can spend quality time with the participants and go over questions and problems in detail. Ken Steele (aka hb), our client software lead developer, will also co-present some material on the structure of the OS on the client and reveal some of the fun features and easter eggs built into it. He will also be available as a Q&A resource during the workshop portion as well. I hope that by the conclusion of the workshop, you will have all the knowledge you will need to start executing your own bitchin’ hardware hacks.

There are nine remaining slots currently available for the talk.

From the horse’s mouth…

Monday, August 28th, 2006

Just for people who are curious about more of the corporate and user aspects of chumby (as opposed to the hacking and engineering aspects, the parts that I’d rather blog about), the CEO of Chumby, Steve Tomlin, has a blog.

Below is a picture of the assembled prototype device (just got a cleaner-looking picture from the Chumby corporate site), and soon I’ll throw up a “virtual chumby” that plays widgets from my chumby account. The virtual chumby renders onto a web page the exact widgets that I look at on my chumby at home by my bed.

(click on picture for a much larger version)

A note about the chumby EULA

Monday, August 28th, 2006

A lot of people have mentioned that the current EULA for chumby is a little bit interesting for an open source project. This post expresses my own opinions about it (not necessarily Chumby’s opinions).

To be honest, it is a work in progress, and we are looking for suggestions to improve it. There is one piece of code on the chumby that is not open source, and that is the Flash player, and Adobe requires us to publish a EULA with our product to protect their proprietary interests. While we evaluated many open source Flash solutions, we found that the Adobe Flash player was the most broadly compatible and had the largest base of developers, something very important for growing a network of content that requires the support and enthusiasm of the Flash artist community.

A problem we found in launching an open source hardware platform is that the traditional mechanisms for open source–GPL, creative commons, etc.–did not have legal language that matched the unique needs of hardware. For example, a creative commons license says nothing about how patents are handled. This is because creative commons cannot be used on functional works. Thus, the creative commons license printed on a chumby core board refers to the mask work only, as that is the only piece of “artwork” that can have a creative commons license validly applied to it. However, I think the final hardware license is fairly tasteful. I fought with our lawyers a bit over it, but I think that in the end it is something I can live with: it explicitly gives you the rights to modify and copy our hardware design kit, and to modify/build your own chumby, and to even resell your modified chumby, as well as kits for modifying it. In particular, academic applications for chumby should have no fear or charge for using any piece of the chumby HDK and SDK in course materials or research apparatus.

There is, however, one clause that says you cannot use the chumby development kit to build or modify chumbys that compete with our widget service. The thing the CEO wants to prevent is someone copying our schematics and plans, and launching a “Crumby” service that leverages our hard work and steals our bacon. I can definitely see his point of view, as the core revenue model–the thing that in part will help pay my salary so I can continue to build hardware that I can share with you in this open-source style–is potentially based on service subscriptions. Note that our plan is to offer a wide variety of widgets for free on our network, so if you get a chumby and don’t buy our service, it is still a pretty useful device, just not as useful as it can be. Plus, if you’re a hardcore open-source guy, you’d hack the hell out of the chumby anyways so you’d have no need to go to our service for widgets (we do not consider you running your own widgets on your own machines as competing with our service–it is your hardware after all–and you aren’t required to buy a subscription). We also plan on being fairly liberal with the ratio of subscriptions to devices, e.g., you are free to copy your subscription within certain boundaries, so you aren’t buying a subscription for every chumby in your house.

Significantly, I want you to be able to use the chumby device with other non-competing networks, such as Skype, IM, or any other thing that may tickle your fancy. The trouble is defining what a competing network is–it’s sort of like Justice Potter Stewart’s famous quote on pornography, “I know it when I see it”. This is something we will hammer out over the next couple of months before our general product deployment phase. While I realize that some of the open-source purists will be put out by the terms like this, the unfortunate reality is that hardware development does cost real money, and so does a colo with servers, and thus a compromise needs to be struck between total openness and a sustainable, protectable business model.

chumby is Free as in “free speech”, but not free as in “free beer”–however, you are free to download the plans for a chumby and brew your own.

chumby–My Inside Perspective

Monday, August 28th, 2006

So, the cat is out of the bag, and I’m finally able to talk about a project that I have had the priviledge of working on for the past several months. I have been working on the chumby, an inexpensive (sub-$150) Wi-Fi enabled content delivery device that is designed to be used around the home. From the hacker’s perspective, chumby is basically a linux client that runs a Flash player and streams content from the “Chumby network”, our content management service. In my mind, these were the goals of the chumby design:

  • simple. A non-hacker user familiar with computers–for example, a typical teenager–should be able to set up and use a chumby. In addition to a lot of thought put into the UI, the chumby network’s ability to deliver drag-and-drop content via Flash widgets is the tehnological cornerstone for chumby’s simplicity. It is this simplicity that differentiates chumby from general purpose devices such as PDAs and laptops.
  • fun. This is a device whose core consumer market is not the gadget fanatic. It needs to be accessible to everyone, so we are trying to take the industrial design in a direction that we like to call the “anti-iPod”.
  • deep. A fatal flaw in many “simple” products is that they are too shallow, and miss key features that would make them useful. Products like the Civa pictureframe, the Ambient Orb, and the Nabaztag rabbit are examples of devices that are too one-dimensional and lack depth. And this leads us up to the most important goal for me–
  • yours. The chumby is architected to be as open as possible to anybody who wants to hack it. In the design of the system, we consider not only open source software hackers, but also hardware hackers and artists and “crafters”–e.g., people who are equally skilled in their ability and passion to do non-computer things, such as metalworking, sewing, carpentry, etc.

Thus, there are two messages about the chumby, neither of which are fundamentally exclusive. One is that Chumby will appeal to the new generation of always-on, always-connected people who use myspace, blogs, and rely on IM to keep in touch (hence the picture of the teenage girl on the chumby corporate website using a chumby). The other is that Chumby will appeal to hackers, who have an insatiable desire to extend, modify, customize, and abuse consumer products to do things they weren’t intended to do. I am hoping that these two worlds will develop a synergy that enables chumby to do things we never imagined.

The real key here is enabling hackers to break out of the realm of point-solution hacks on unsupportable hardware and into the realm of something you can share with hopefully just about anyone. My boss likes to cite the example of a hack where someone adds a blood pressure cuff to chumby, and gives it to their grandmother. Now you can check on grandma’s health, and she can watch pictures of her grandchildren while she gets her bloodpressure taken. Now imagine this scenario, but with a WRT-54G router instead of a chumby. Sure, you can add a blood pressure cuff to a WRT-54G as well (they are architecturally quite similar in fact), but try to explain to grandma how to set it up and use it. In other words, hackers can leverage the effort we spent into making chumby usable to help make their hacks more usable and more palatable to others.

So, Chumby is making the source code, schematics, board layouts, bill of materials, flat patterns and 3-D CAD databases of our plastic pieces available for you to use. You can find them all at the chumby developer site (the link may be down right now due to the stress on our servers from being on digg, engadget, and other popular websites). Working on chumby is very personally exciting to me, because not only am I presented with the opportunity to build a product that helps people improve their lives in some small way, there is also a chance for me to enable you to build hacks on this platform, and you can leverage our (hopefully) success.

Here is a simple example of what I mean. I heard from someone this weekend at FOO camp (I forget who already–if you are reading, please refresh my memory!) that they are unhappy that the thermostat in their home is so far away from the place where they actually want to have thermoregulation. Thus, a weekend project for him would be to hack a chumby and add a temperature sensor. Since the chumby platform already has Wi-Fi built into it, the amount of hardware grunge work he has to do is minimal–he just needs two chumbys, one with a temperature sensor, and one with an interface to the thermostat, both enabled with the hacker sensor package that I built (more on that later). Furthermore, the device he builds will not only help keep his livingroom at the right temperature, it can also tell him the latest news and help him track his favorite TV shows. The coup de grace for all of this is that he is also free to publish his modifications and even resell modified chumbys with this capability so that others can enjoy the benefits of his work, and he can make some profit off of his initiative. And on a lighter note, since the housing itself is made out of fabric, he has the opportunity to redo the housing so that it matches the livingroom decor, keeping his spouse happy because there is not yet another odd hack with ugly cords everywhere sitting in the livingroom.

And of course, I want to make clear that I’m not the only guy behind Chumby–I am just the hardware lead designer, and I do the linux kernel stuff too (which is something new for me, but it was a lot of fun learning the insides of linux from boot to halt). There’s a team of talented, hard-working people who are also a lot of fun to work with.

Winner of Name that Ware August 2006!

Monday, August 28th, 2006

So, this ends the lightning round for Name that Ware August 2006! I feel compelled to select two winners: the best answer pre-chumby public disclosure, and the first answer post-chumby disclosure. So, the winners are Ian for his thoughtful post on August 26th, and Dan Lane for his quick post on August 27th (how did you find out about this so quickly??). Contact me to collect your prize!

So, indeed, this is a chumby core board! I was embargoed from posting about chumby until our product introduction at FOO camp 2006, although I was allowed a slight (just one day) lead on releasing board photos with identifying text redacted.

It was most interesting to read people’s thoughts about the chumby device, especially since the early posters did not have the benefit of the chumby PR materials to crib off of.

I’ll go over the details of the chumby hardware in my next couple of posts–I think I’ll split them up to make them more readable and topical.