While at Liverpool Makefest last June, I bought myself a kit to build an RC2014 Z80-based computer.
The kit was very well made, with high quality circuit boards which accepted solder very easily, along with sufficient documentation to make the whole building process smooth and enjoyable.
I found the process quite educational too, as the design of the kit splits out the various functions of a computer into separate boards which then plug into a backplane with a common bus linking the parts together. It was good to see how the CPU, ROM, RAM, Clock and I/O all work together to make a functional microcomputer.
I was able to talk to the RC2014 from another computer over a serial connection, but I found I got the real ‘retro’ feel when I added the RC2014 ‘video card’ – which is a serial terminal based on a Raspberry Pi Zero. This meant I could plug my creation into a monitor and keyboard without the need for a separate computer, making the whole thing into a self-contained 8-bit microcomputer.
I also added an I/O board of LEDs and switches so I could interact with the computer without the need for a monitor or keyboard.
Chromebooks are nice machines, but of course they dance to Google’s tune. Google are usually pretty good at adopting open standards but occasionally they think they can do better. There are established protocols for printing over a network, but Google have ignored these entirely by ensuring that all Chromebooks only support Google Cloud Print printers!
To be fair to the mighty G, they do explain how you can leave a PC running with their Google Chrome browser open to make your existing printer available to your Chromebooks but electricity on the Isle of Man is not very cheap, so I don’t want to leave a PC running all day long.
Instead, I’ve deployed a humble Raspberry Pi along with the magic of GNU/Linux and the Google Cloud Print connector for CUPS to achieve the same result without wasting the planet’s resources.
However, efficiently sipping electricity like this won’t help the island to pay off its debts!
While I was in the UK recently, I took advantage of an Argos store to acquire a USB Wireless dongle. I bought the TP-Link TL-WN725N because it was cheap, and very small. The plan was to use it with my Raspberry PI, and a quick Google suggested the TL-WN725N would run directly from the Raspberry Pi without needing external power, and the driver was already baked into the kernel.
Of course, nothing in life is ever simple. It turns out that TP-Link have recently changed the chip inside the adapter, and are now selling version 2.0 of the device. This would be great (newer hardware is always better, right?) apart from the fact that the kernel in the Raspian linux I use on my Rasperry Pi does not have the correct driver for this new chip.
Luckily, the new chip is manufactured by Realtek who are such a great company they release driver source code for their devices. So, on my to-do list now is to compile the new wireless driver for my Raspberry Pi kernel. I suspect compiling from source will take quite a while on the humble ARM processor in the Raspberry Pi…