ARM Mali-200 and Mali-400 GPU Open Source Driver Released

There has been a lot of controversy around GPU drivers and open source, as GPU drivers usually come with a blob (a binary file). If you have been lurking in Raspberry Pi forums you’ll know what I mean. But this will change thanks to Lima. No, not the capital of Peru but the open source graphics driver for ARM Mali GPUs (Mali-200 and Mali-400) also called Lima whose goal is stated as follows: The aim of this driver is to finally bring all the advantages of open source software to ARM SoC graphics drivers. Currently, the sole availability of binary drivers is increasing development and maintenance overhead, while also reducing portability, compatibility and limiting choice. Anyone who has dealt with GPU support on ARM, be it for a Linux with a GNU stack, or for an Android, knows the pain of dealing with these binaries. Lima is going to solve this for you, but some time is needed still to …

Android Kernel Source Released for HP TouchPad

The CyanogenMod team has been working on an Android port for the HP TouchPad for a while, and although good progress has been made, the firmware is still considered alpha due to issues with hardware and driver support. There are 2 versions: CM 7 (Alpha) with Android 2.3 and CM 9 (Alpha) with Android 4.0. The CM7 version is more complete and stable than CM9. The Android port might be sped-up as following pressure from the developer community, Hewlett Packard has released the Android kernel source and some other GPL packages modified for the HP TouchPad. Apparently, HP used those for factory testing. The source code is available on github at https://github.com/dalingrin/hp-kernel-tenderloin/tree/hp-topaz-android “green” user at rootzwiki built the kernel binary which is available at  http://crimea.edu/~green/TP/oss-db910-QC1065-Kernel.tar.bz2 They also have the source code for: androidvncserver: http://crimea.edu/~green/TP/oss_db910_vnc.tar.bz2 i2c-tools: http://crimea.edu/~green/TP/oss_db910_i2c.tar.bz2 Apparently all components needed are available, except the wifi driver (Atheros AR6003), which HP may also release a bit later as it might also …

HP Releases Open WebOS 1.0 Roadmap and Enyo 2.0 Source Code

HP announced further details on webOS including a roadmap & its license and released Enyo 2.0 source code. The webOS code will be made available under the Apache License, Version 2.0, beginning with the source code for Enyo. Enyo is a Javascript development platform allowing developers to write applications that works across mobile devices and desktop web browsers, from the webOS, iOS and Android platforms to the Internet Explorer and Firefox browsers. webOS roadmap Here’s webOS roadmap until September 2012: January – Enyo 2.0 and Enyo source code released under Apache License, Version 2.0 February – Intended project governance model, QT WebKit extensions, JavaScript core and UI Enyo widgets March – Linux standard kernel, Graphics extensions EGL, LevelDB and USB extensions April – Release of Ares 2.0, Enyo 2.1 and Node services July – System manager (“Luna”), System manager bus, Core applications and Enyo 2.2 August – Build release model and Open webOS Beta September – Open webOS 1.0 Release …

Always Innovating Unveils Open Source Android 4.0 HDMI Dongle STB

Always Innovating announced the “HDMI Dongle”, an open source portable STB that runs Android 4.0 on a Texas Instruments OMAP4 processor clocked between 1 and 1.8GHz with 256MB to 1GB of RAM, a microSD slot, Wi-Fi, Bluetooth and a remote control that provides NFC & accelerometers. The HDMI Dongle is a device of the size of a USB stick that can be plugged into any HDMI port to transform a any HDMI (and USB) capable TV into a smart TV. The USB port is used to power the device. The company says the HDMI Dongle is “technically compatible with GoogleTV”, which probably means it is not yet supported, but a software upgrade could enable Google TV for Android 4.0. The device provides a full-compatible Android experience and any application for this operating system can run on the dongle. The HDMI Dongle can stream and decode from the Internet 1080p H.264 video. The user interface is controlled with a 9-button remote …

Amazon Kindle Fire Source Code Available

After Android 4.0 source code release, it’s a good week for open source, as Amazon has also opened Kindle Fire source code as it had to comply with Android Open Source Project (AOSP) license has some point. Source code for other Kindle products is also available. The source code for the Kindle Fire is tarred in a file named Kindle_src_6.2_11185402.tar.gz which is quite a large download (809 MB).  The file contains 4 directories with the source code for the Linux kernel (2.6.35), a modified version of Android 2.2, the bootloader (u-boot) and x-loader, first-level bootloader for OMAP SoC. I’m not sure many people will work on this version, as Android 4.0 source code for OMAP4 (The processor used in Kindle Fire) is available and has been ported to Galaxy Nexus and TI OMAP4 low cost development board (Pandaboard). So we could see Android 4.0 (ICS) running on Kindle Fire in the near future. Memory optimization may have to be done …

Android 4.0 Source Code is Now Available

Google has just released Android 4.0.1 source code in AOSP. There are 3 main branches: android-4.0.1_r1: the release branch, ITL41D, that is expected to ship on Galaxy Nexus. That’s the one you want to be using to port to devices. ics-mr0: ICS development branch. It contains a few changes that aren’t in the release branch, so it might not be as stable. That’s the one you want to use if you plan to contribute to CTS. master: usual master branch, it contains all of ics-mr0 plus a few extra changes. That’s the branch that you should use if you want to contribute to the platform. The release and development branch require the “classic” host configurations (Ubuntu 10.04, or MacOS 10.6 with XCode 3). The master branch had a few tweaks to make it work better on newer systems  (Ubuntu 11.10, Mac OS 10.7 with XCode 4.2) but it’s not 100% there yet. In addition to the usual emulator targets and …

Android 4.0 Source Code To Be Released When Galaxy Nexus Ships

Google never opened Android 3.0 (Honeycomb) source code. It was probably because this OS was only meant to be used with tablets and they feared people would try to use it on smartphone. The good news is that Android 4.0 (ICS) source code will be made available once the Galaxy Nexus ships. Although I’m not sure what license will be used with Android 4.0, that follows exactly the GPL license requirements since you don’t need to release the source code if you don’t provide the binaries. See Jean-Baptiste Queru (Android Open Source Project ) announcement at https://plus.google.com/112218872649456413744/posts/HB5qQHeNKBQ. In the meantime, the GPL source files that match the Android 4.0 / r14 SDK have been made available: Kernel: https://dl.google.com/dl/android/gpl/android-gpl-kernel-sdk-4.0.1_r1.tgz Platform: https://dl.google.com/dl/android/gpl/android-gpl-platform-sdk-arm-4.0.1_r1.tgz Dev Tools: https://dl.google.com/dl/android/gpl/android-gpl-tools_r14.tgz Extra: https://dl.google.com/dl/android/gpl/android-extra-4.0.1-r14.tgz Like the Android did for all Honeycomb release, this is NOT the full source tree for Android 4.0 (ICS), these are only the GPL parts that are in the SDK (along with a few associated …

Online Petition Requesting to Allow Linux Installation on Windows 8 Devices

Back in September, some concerns emerged about UEFI secure boot requirement for Windows 8 and its possible consequences on Linux and other open source operating systems: it may be impossible to install such systems on computers or devices shipped with Windows 8, either by replacing Windows 8 or in a dual boot installation as the bootloader (UEFI) would prevent such installation for security reasons. Microsoft has already replied to those concerns and stated that: At the end of the day, the customer is in control of their PC. … We work with our OEM ecosystem to provide customers with this flexibility. The security that UEFI has to offer with secure boot means that most customers will have their systems protected against boot loader attacks. For the enthusiast who wants to run older operating systems, the option is there to allow you to make that decision. So there should be an option to disable/enable “Attempt Secure Boot” as shown below (UEFI …