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.

HTC’s designers interrogated for stealing trade secrets

Earlier today, several top designers at HTC were arrested in Taipei under suspicion of fraudulent expense claims, as well as stealing trade secrets ahead of leaving the company to run a new mobile design firm in both Taiwan and mainland China. Five people were interrogated, with the most notable ones being Vice President of Product Design Thomas Chien, R&D director Wu Chien Hung and design team senior manager Justin Huang (who also personally sketched out the One's design). Chien and Wu are taken into custody, whereas the others were released on bail. Their offices were also raided yesterday as part of the investigation.

HTC certainly looks like a sinking ship, doesn't it?

Former White House ‘copyright czar’ becomes CEO of BSA

Victoria Espinel, who until recently served as the White House's first intellectual property enforcement coordinator, will now head one of the most powerful trade groups in the tech industry. She's been tapped to become the new president and CEO of The Software Alliance (or BSA) starting September 3rd. In her new role, she'll be tasked with pushing the anti-piracy interests of major players like Microsoft, Dell, Apple, Oracle, and Intel. And while the BSA spends a large part of its time lobbying Congress and other governments to push that agenda, Espinel will be barred from engaging in such practices herself - at least initially. According to Politico, an ethics pledge Espinel took to secure her "copyright czar" position under President Obama prevents her from lobbying for at least two years.

No corruption here. Nothing to see. Move along.

BlackBerry on the Ropes

According to a Computerworld article, BlackBerry is exploring putting itself up for sale, as the company falls into 4th place in the mobile market. IDC statistics that show Android leads the mobile market with nearly 80%, iOS has 13.2%, Windows Phone 3.7%, and BlackBerry 2.9%. Gartner analyst Bill Menezes states that even new ownership is "not going to address how the company restores itself."

One key asset BlackBerry owns is QNX, the real-time based OS it bought in 2010. QNX is microkernel based, versus the monolithic kernel used by many OS's like Linux. BlackBerry bases its tablet and phone OS's on QNX, which also remains a popular commercial OS for embedded systems.

Nintendo unveils 2DS

The new Nintendo 2DS system gives you all the features of the Nintendo 3DS and Nintendo 3DS XL, minus 3D viewing. And the price makes the world of Nintendo games even more accessible.

Curiously enough, the 2DS actually has only one screen - it's divided in two by the casing. The entire screen is touch-capable, but the top screen is covered by plastic so you can't touch it there. Like the Wii U's controller, this thing just looks weird and unwieldily, and while the price is nice, I doubt it will turn Nintendo's fortunes around.

Imagine a phone and/or tablet designed and built by Nintendo, with a proper integrated gamepad, capable of output to external displays, with access to Nintendo's entire back catalog of games - from the NES, through the Game Boy, SNES, Nintendo64, GameCube, DS, and Wii (if compatible with non-motion controls). Of course, new games can be published as well.

Nintendo should not be making yet another device to carry aside from your phone. They should be making a phone.

Ranking of companies by number of NPE lawsuits

As of August 2013, PatentFreedom has identified and profiled over 710 distinct NPEs (a number which continues to increase). Since 1985, these NPEs have been involved in litigation with over 10,000 different operating companies in nearly 11,000 actions, for a total of over 30,000 events. There are clear indications that NPEs in recent years increasingly seek to enforce their patents against companies of all sizes and in many industries. Despite this trend, as the table below shows, NPEs continue to target many large and high-profile companies quite relentlessly.

Virtually all large technology companies are increasingly being targeted by patent trolls. I shed no tears for any of them, though. Offensive abuse of (software/design) patents is always wrong, whether you produce products or not.

You reap what you sow. These companies actively lobby to keep the patent system as it is, and as such, they deserve exactly what they're getting.

Hangouts goes HD, H.264 to VP8, WebRTC up next

Noticed any differences when using Google's Hangouts video chat lately? If you did, then you may be one of the lucky users who has already received an upgrade to 720p HD video. The company quietly started to roll out HD for Hangouts to a subset of its users in the last few weeks and hopes to complete the rollout soon. But the change isn't just a quality upgrade - it's part of a bigger move towards open standards that will eventually bring us video chat in the browser without the need for any plugins.

To enable HD, and prepare for this plugin-free future, Google quietly started to transition Hangouts from the H.264 video codec to VP8, an open and royalty-free video codec the company released back in 2010. Google's Vice President of Engineering Chee Chew told me during a recent interview that the switchover from H.264 to VP8 should be more or less invisible to consumers, with some possibly noticing a little less choppiness. "It will be cleaner, better video," Chew said.

Good move.

On a related note, whatever happened to Apple's promise to make FaceTime an open standard?

New Zealand definitively bans software patents

New Zealand has finally passed a new Patents Bill that will effectively outlaw software patents after five years of debate, delay and intense lobbying from multinational software vendors.

Aptly-named Commerce Minister Craig Foss welcomed the modernisation of patents law, saying it marked a "significant step towards driving innovation in New Zealand".

"By clarifying the definition of what can be patented, we are giving New Zealand businesses more flexibility to adapt and improve existing inventions, while continuing to protect genuine innovations," Foss said.

It's too bad that - no matter how awesome New Zealand is - they're a very small player, much like my own country. Still, change has to start somewhere, and this is at least something.

Google cripples AllCast for ChromeCast

Update: the functionality used by the application was reverse engineered and Google stated that it may change. Google has released a statement which acknowledges that playing local content will come back to ChromeCast once the API has stabilised. Storm in a teacup, apparently.

Heads up. Google's latest Chromecast update intentionally breaks AllCast. They disabled 'video_playback' support from the ChromeCast application.

Given that this is the second time they've purposefully removed/disabled the ability to play media from external sources, it confirms some of my suspicions that I have had about the Chromecast developer program: the policy seems to be a heavy handed approach, where only approved content will be played through the device.

A company intentionally disabling cool stuff? Surely you jest.