Cubox [Part 4]: usb wifi + kernel build

Ideally a Ralink so I grabbed a cheap D-Link Wireless N 150 USB adapter:


[93379.042492] usb 1-1: new high speed USB device using orion-ehci and address 2
[93379.211469] usb 1-1: New USB device found, idVendor=07d1, idProduct=3c16
[93379.218616] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[93379.226201] usb 1-1: Product: 11n Adapter
[93379.230249] usb 1-1: Manufacturer: Ralink
[93379.234729] usb 1-1: SerialNumber: 1.0
[93379.240455] usb 1-1: configuration #1 chosen from 1 choice
[93861.002520] backlight power down

Debian wiki shows the way forward http://wiki.debian.org/rt2870sta 

Sadly the modules that have been built for the stock kernel .. however in the wonderful world of openness the lovely folk at solid-run.com have the kernel on github   https://github.com/rabeeh/linux-2.6.32.9 so I can simply clone it and build (no huge reason to make a massive jump yet).

Watch this space ...

Google code Import from git

Working through pushing out ENUM Discoverer git repo to Google codes SVN repo. Not 100% what the outcome will be like - it's still posting the entire history.

Personally I need to do a lot more work with git to be happy rebase-ing. At the moment whilst I (think I) understand the concepts of migrating a linear time-line to SVN I'm not sure what how accurate the time-line will be pushing to SVN will be. Quite a few merges were required and I didn't spend a great deal of time reviewing in detail. To keep the SVN conversion process clean we may tweak our commit process.