Keep OSNews alive by becoming a Patreon, by donating through Ko-Fi, or by buying merch!

Monthly Archive:: September 2013

The Z-80 has a 4-bit ALU – here’s how it works

The 8-bit Z-80 processor is famed for use in many early personal computers such the Osborne 1, TRS-80, and Sinclair ZX Spectrum, and it is still used in embedded systems and TI graphing calculators. I had always assumed that the ALU (arithmetic-logic unit) in the Z-80 was 8 bits wide, like just about every other 8-bit processor. But while reverse-engineering the Z-80, I was shocked to discover the ALU is only 4 bits wide! The founders of Zilog mentioned the 4-bit ALU in a very interesting discussion at the Computer History Museum, so it's not exactly a secret, but it's not well-known either.

I have been reverse-engineering the Z-80 processor using images from the Visual 6502 team. The image below shows the overall structure of the Z-80 chip and the location of the ALU. The remainder of this article dives into the details of the ALU: its architecture, how it works, and exactly how it is implemented.

Ken Shirrif's blog is an absolute must for fans of ultra-low-level hardware stuff. This goes way over my head, but interesting nonetheless.

How Chrome Apps will finally take on Windows

The new apps look and behave much like the native apps you find on Windows and OS X. They're built using web technologies, but also with Chrome-specific code that means they won't be able to run on other web browsers - they're truly Chrome apps. They can exist outside of your browser window as distinct apps, work offline, and sync across devices and operating systems. They can also access your computer's GPU, storage, camera, ports, and Bluetooth connection. Chrome Apps are, for now, only available through Chrome on Windows or Chrome OS on a Chromebook. Mac users will have to wait another six weeks before their version of Chrome will be updated.

This is very important for Chrome OS - since this means it can now have applications outside of the browser. Google's plans for Chrome OS suddenly became a whole lot clearer.

Samsung Galaxy Gear unveiled

The Verge on the Galaxy Gear:

There are a couple of significant downsides that temper my enthusiasm for the new Gear. First and foremost is the speed and intuitiveness of the user interface - or rather, the lack thereof. There's a tangible lag to anything you do with the Gear, while the swipe gestures are hard to figure out and do different things depending on where you are in the menus.

Also important will be the Galaxy Gear's battery life. It does use the Bluetooth 4.0 Low Energy standard to communicate, but at 315mAh its battery is decidedly small. Samsung promises "about a day" of endurance from the Gear, but by the end of our briefing with the company, the cameras on most of its demo units were refusing to turn on due to the watches running low on power.

Yeah, no. I don't know what a smartwatch is, but this, is not it.

Nokia confirms: its patent attacks may continue

Microsoft paid billions for a license to Nokia's patents, but the company has made explicit that Nokia still owns the patents. The genius of this move is that it allows Microsoft to double down on its patent war with Android. Microsoft boasts that the majority of Android phones sold worldwide have already paid for a license to Microsoft patents. By 2011, patent licensing revenue exceeded Microsoft's revenue from Windows Phone.

Now, Nokia can go after Android phone makers for royalties - even ones that have already paid Microsoft.

When pressed on the issue today, a Nokia spokesman confirmed that more patent licensing is indeed part of the plan.

So, without products, Nokia will become a true patent troll. Good to know.

Microsoft raced to deal with soul-searching Nokia

Microsoft's agreement to buy Nokia's handset business, codenamed Project Gold Medal, was more of a sprint than a marathon.

Talks between the two companies began in February after both sides agreed a two-year-old collaboration on smartphone development wasn't working, according to people familiar with the deal.

This cannot be true. Internet commenters told me in no uncertain terms that Nokia and Windows Phone were doing just fine. And internet commenters are always right.

Google unveils Android KitKat

Android is the operating system that powers over 1 billion smartphones and tablets. Since these devices make our lives so sweet, each Android version is named after a dessert: Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, Ice Cream Sandwich, and Jelly Bean. As everybody finds it difficult to stay away from chocolate we decided to name the next version of Android after one of our favorite chocolate treats, Kitkat!

Not a whole lot of information just yet. The page says "It's our goal with Android KitKat to make an amazing Android experience available for everybody", which could mean either a focus on lower-end, cheaper devices, improved support for more form factors such as laptops, or both.

As for the name - the BBC reports that Nestle is okay with Android using the KitKat name, and that no money is exchanging hands. A deal was reached within 24 hours.

The Nokia 8800

In light of today's news, this is my favourite Nokia device of all time. The 8800 was gallery play in design, construction, and attention to detail. Not even today's phones come even close to how beautiful, sleek, and incredibly sturdy the 8800 felt. I reviewed it for OSNews way back in 2006.

The slider mechanism used ball bearings. Ball bearings.

Google is defragging Android

Google's strategy is clear. Play Services has system-level powers, but it's updatable. It's part of the Google apps package, so it's not open source. OEMs are not allowed to modify it, making it completely under Google's control. Play Services basically acts as a shim between the normal apps and the installed Android OS. Right now Play Services handles the Google Maps API, Google Account syncing, remote wipe, push messages, the Play Games back end, and many other duties. If you ever question the power of Google Play Services, try disabling it. Nearly every Google App on your device will break.

Fragmentation addressed through the backdoor. Too bad it's too technical for most blogs, so the fragmentation line will be parroted for years and years to come.

Tide rolls in: Microsoft acquires Nokia’s devices unit

Ever since Stephen Elop became CEO of Nokia we knew this outcome was inevitable. It was his job to make it as easy as possible for Microsoft to acquire the vital parts of Nokia, and here we are: Microsoft is acquiring Nokia's devices unit for 3.79 billion euro, and another 1.65 billion euro for its patents. It's a bit of a complicated deal in that Microsoft buys the Asha feature phone brand and Lumia smartphone brand outright, but will only license the Nokia name for current Nokia products; the Nokia brand will remain under the control of Nokia the company. This means Nokia as a phone brand is effectively dead.

In addition, Stephen Elop will return to Microsoft. I'm sure entirely coincidentally, Ballmer announced recently that he's stepping down.

All this was as inevitable as the tides rolling in. Nokia has been going downhill and has stagnated ever since the announcement it would bank its future on Windows Phone. It went from being the largest smartphone manufacturer to an also-ran, which is made painfully clear by the fact that Microsoft paid more for Skype than it does for Nokia's devices unit.

A painful end for a once-great phone brand. This was the plan all along, and in essence, Nokia's board has executed it masterfully; the Finnish company has switched core markets several times in its long, long history (it started out as a paper company), and the unprofitable phone business was a huge liability for the company, despite claims by some that Nokia was doing just fine. Nokia's board has masterfully gotten rid of this money pit so it can focus on the parts that are profitable.

And, as always, the next Lumia will turn it all around.