Skip to main content

This is the future(SoC) - from infoQ


Microsoft has announced they are working on bringing Windows to the SoC platform enabling software and hardware manufacturers to target devices having all sorts of form factors and running on Microsoft’s operating system.
During CES  2011, Microsoft announced that the future version of Windows will support System-on-a-Chip (SoC) platforms. SoC are an attempt to integrate as many components as possible in a single chip, which is supposed to offer the computability power of a full size system but taking a lot less space and, especially, consuming less power. They announced work in progress to make Windows run on SoC from NVIDIA, Qualcomm and Texas Instruments, all built on an ARM architecture. In the same time, Intel and AMD will continue to innovate on their x86 32-bit and 64-bit platforms in order to create SoC platforms for Windows.
Mike Angiulo, Corporate Vice President, Windows Planning, Hardware & PC Ecosystem, at Microsoft, demoed a version of Windows running on an Intel Atom SoCs during Steve Ballmer’s keynote at CES. The version of Windows prototype shown was a Windows 7 enhanced to run on Atom and ARM. The SoC is the size of a thumbnail and it’s motherboard the size of a small phone, being able to be built into a phone along with a battery and a screen, yet in the same time being able to run a full blown version of Windows. According the Angiulo, the Intel Atom SoC is compatible with “all the existing software and hardware applications that run on Windows today”, “anything that works on Windows, works right out of the box here”.
Angiulo also showed running Windows on Snapdragon from Qualcomm, on OMAP from Texas Instruments, and on Tegra from NVidia, all based on an ARM architecture. Unlike natively running on Intel’s Atom, Windows applications need to be recompiled in order to be running on ARM. He showed Word, PowerPoint, hardware accelerated HTML5 in IE9, full HD video, all running on ARM. He also printed a page on a regular printer after the print driver was recompiled for ARM. The advantage of the ARM-based platforms is a very low power consumption.
Windows for SoC will open the opportunity for Microsoft and manufacturers to target all sorts of devices, in all form factors, bringing the entire Windows ecosystem, the operating system and applications built for it, to tablets, energy efficient netbooks and laptops, Surface, and other devices that might appear in the future. They could target even smartphones, but that is a strange idea considering Microsoft already has Phone 7 for that.
There was no roadmap presented. It is not known when this version of Windows will be production ready, or what it is going to be called. Most probably, it will be a flavor of version 8 of Windows.
Labels:

Comments

Post a Comment

Popular posts from this blog

Quicksort implementation by using Java

 source: http://www.algolist.net/Algorithms/Sorting/Quicksort. The divide-and-conquer strategy is used in quicksort. Below the recursion step is described: 1st: Choose a pivot value. We take the value of the middle element as pivot value, but it can be any value(e.g. some people would like to pick the first element and do the exchange in the end) 2nd: Partition. Rearrange elements in such a way, that all elements which are lesser than the pivot go to the left part of the array and all elements greater than the pivot, go to the right part of the array. Values equal to the pivot can stay in any part of the array. Apply quicksort algorithm recursively to the left and the right parts - the previous pivot element excluded! Partition algorithm in detail: There are two indices i and j and at the very beginning of the partition algorithm i points to the first element in the array and j points to the last one. Then algorithm moves i forward, until an element with value greater or equal
Post a Comment
Read more

Live - solving the jasper report out of memory and high cpu usage problems

I still can not find the solution. So I summary all the things and tell my boss about it. If any one knows the solution, please let me know. Symptom: 1.        The JVM became Out of memory when creating big consumption report 2.        Those JRTemplateElement-instances is still there occupied even if I logged out the system Reason:         1. There is a large number of JRTemplateElement-instances cached in the memory 2.     The clearobjects() method in ReportThread class has not been triggered when logging out Action I tried:      About the Virtualizer: 1.     Replacing the JRSwapFileVirtualizer with JRFileVirtualizer 2.     Not use any FileVirtualizer for cache the report in the hard disk Result: The japserreport still creating the a large number of JRTemplateElement-instances in the memory        About the work around below,      I tried: item 3(in below work around list) – result: it helps to reduce  the size of the JRTemplateElement Object        
1 comment
Read more

Stretch a row if data overflows in jasper reports

It is very common that some columns of the report need to stretch to show all the content in that column. But  if you just specify the property " stretch with overflow' to that column(we called text field in jasper report world) , it will just stretch that column and won't change other columns, so the row could be ridiculous. Haven't find the solution from internet yet. So I just review the properties in iReport one by one and find two useful properties(the bold  highlighted in example below) which resolve the problems.   example: <band height="20" splitType="Stretch" > <textField isStretchWithOverflow="true" pattern="" isBlankWhenNull="true"> <reportElement stretchType="RelativeToTallestObject" mode="Opaque" x="192" y="0" width="183" height="20"/> <box leftPadding="2"> <pen lineWidth="0.25"/>
4 comments
Read more