SOURCE: http://www.xda-developers.com/android/broadcom-releases-videocore-source-ported-to-bcm21553-socs/
LINK: http://blog.broadcom.com/chip-desig...ves-developers-keys-to-the-videocore-kingdom/
The community of open source mobile developers around the world are a vocal bunch – and here at Broadcom we’ve heard their call.
To date, there’s been a dearth of documentation and vendor-developed open source drivers for the graphics subsystems of mobile systems-on-a-chip (SoC). Binary drivers prevent users from fixing bugs or otherwise improving the graphics stack, and complicate the task of porting new operating systems to a device without vendor assistance.
But that’s changing, and Broadcom is taking up the cause.
Today, Broadcom is releasing the full source of the OpenGL ES 1.1 and 2.0 driver stack for the Broadcom VideoCore® IV 3D graphics subsystem used in the BCM21553 3G integrated baseband SoC. VideoCore IV is used in many Broadcom products, including the BCM2835 application processor, which runs the popular Raspberry Pi microcomputer.
The trend over the last decade has leaned towards greater openness in desktop graphics, and the same is happening in the mobile space. Broadcom — a long-time leader in graphics processors — is a frontrunner in this movement and aims to contribute to its momentum.
The VideoCore driver stack, which includes a complete standards-compliant compiler for the OpenGL® ES Shading Language, is provided under a 3-clause BSD license; the source release is accompanied by complete register-level documentation for the graphics engine.
HOPE THIS HELPS OUR BELOVED DEVELOPERS AT SAMSUNG GALAXY GRAND DUOS (GT-I9082) FORUM TO DEVELOP MORE AWESOME ROMs!
Good Luck Guyz :good:
Related
Not that important yet, but worth checking.
Main target is i5700, but maybe there may be an open-source PowerVR driver for Linux with benefit for GalaxyS as well.
There Might Be An Open PowerVR Driver In Q3'11
http://www.phoronix.com/scan.php?page=news_item&px=OTAzNg
Will see.
Thx for info!
Q3 2011?
mmm...i hope sooner!
We need more power and graphics driver can make a difference.
But AMD/ATI made open driver soo long time ago, and we still never get even equal driver.
can anyone explain in brief that what is tegra, powervr, qualcomm, snapdragon... i want to run dungeon hunter on my wildfire and i ahve read many reviews about tegra and powervr but i am still unable to understand..can anyone help...???
Tegra, developed by Nvidia, is a system-on-a-chip series for mobile devices such as smartphones, personal digital assistants, and mobile Internet devices. The Tegra integrates the ARM architecture processor central processing unit (CPU), graphics processing unit (GPU), northbridge, southbridge, and memory controller onto one package. The series emphasizes low power consumption and high performance for playing audio and video.
Qualcomm (NASDAQ: QCOM) is an American global telecommunication corporation that designs, manufactures and markets digital wireless telecommunications products and services based on its code division multiple access (CDMA) technology and other technologies. Headquartered in San Diego, CA, USA. The company operates through four segments: Qualcomm CDMA Technologies (QCT); Qualcomm Technology Licensing (QTL); Qualcomm Wireless & Internet (QWI), and Qualcomm Strategic Initiatives (QSI).
PowerVR is a division of Imagination Technologies (formerly VideoLogic) that develops hardware and software for 2D and 3D rendering, and for video encoding, decoding, associated image processing and Direct X, OpenGL ES, OpenVG, and OpenCL acceleration.
Snapdragon is a family of mobile system on chips by Qualcomm. Qualcomm considers Snapdragon a "platform" for use in smartphones, tablets, and smartbook devices.
The Snapdragon application processor core, dubbed Scorpion, is Qualcomm's own design. It has many features similar to those of the ARM Cortex-A8 core and it is based on the ARM v7 instruction set, but theoretically has much higher performance for multimedia-related SIMD operations.
I did not understand your question btw.
Our little wildfire has no GPU so you probably wont be able to run high-end games smoothly!
yash_p90 said:
Tegra, developed by Nvidia, is a system-on-a-chip series for mobile devices such as smartphones, personal digital assistants, and mobile Internet devices. The Tegra integrates the ARM architecture processor central processing unit (CPU), graphics processing unit (GPU), northbridge, southbridge, and memory controller onto one package. The series emphasizes low power consumption and high performance for playing audio and video.
Qualcomm (NASDAQ: QCOM) is an American global telecommunication corporation that designs, manufactures and markets digital wireless telecommunications products and services based on its code division multiple access (CDMA) technology and other technologies. Headquartered in San Diego, CA, USA. The company operates through four segments: Qualcomm CDMA Technologies (QCT); Qualcomm Technology Licensing (QTL); Qualcomm Wireless & Internet (QWI), and Qualcomm Strategic Initiatives (QSI).
PowerVR is a division of Imagination Technologies (formerly VideoLogic) that develops hardware and software for 2D and 3D rendering, and for video encoding, decoding, associated image processing and Direct X, OpenGL ES, OpenVG, and OpenCL acceleration.
Snapdragon is a family of mobile system on chips by Qualcomm. Qualcomm considers Snapdragon a "platform" for use in smartphones, tablets, and smartbook devices.
The Snapdragon application processor core, dubbed Scorpion, is Qualcomm's own design. It has many features similar to those of the ARM Cortex-A8 core and it is based on the ARM v7 instruction set, but theoretically has much higher performance for multimedia-related SIMD operations.
I did not understand your question btw.
Our little wildfire has no GPU so you probably wont be able to run high-end games smoothly!
Click to expand...
Click to collapse
can chainfire 3d solve this problem??
wild[email protected] said:
can chainfire 3d solve this problem??
Click to expand...
Click to collapse
How can it work on our wildfire. It is for devices which HAVE a GPU!!
And Chainfire3D has been tested only on:
- HTC HD2 (2.3.3 / NAND)
- Samsung Galaxy S (2.3.3)
- Samsung Galaxy Tab 7" (2.3.3)
- Samsung Galaxy S II (2.3.3)
- Motorola Atrix 4G (2.2.1)
- Motorola Droid 2
- LG Optimus 2X (2.3.4)
MOREOVER, Chainfire3D is for 1ghz+ devices only
So..I hope you get your answer!
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
Read this:
Chainfire3D is an intermediary OpenGL driver. What does that mean? It means that Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
phoronix reported this today:
"There is some exciting news to break today on Phoronix... Coming up at FOSDEM (the Free Open-Source Developers' European Meeting in Brussels) will be the formal announcement of an open-source, reverse-engineered graphics driver for the ARM Mali graphics processor. OpenGL ES triangles are in action on open-source code. Will this be the start of fully open-source ARM graphics drivers for Android and Linux?"
is this relevant to our dev community? isn't this one of the obstacles in getting CM9 on our phones?
Wow...maybe this will help fix our slightly-off crt off animation. Exciting stuff
Sent from my SPH-D710 using xda premium
...or what about Hw acceleration for everything?
About The Eye Tribe
The Eye Tribe is an exciting startup based in Copenhagen developing eye tracking technology that can be integrated into a wide range of products like mobile phones, tablets, computers, monitors and cars. The Eye Tribe has been named Cool Vendor 2012 by Gartner, and has won numerous awards since the company was founded in 2011.
About the job
The Lead Android developer will be responsible for leveraging our technology to the Android platform, working together with our eye tracking algorithm experts to build the next generation Human-Computer Interaction technology for the Android platform.
We seek a professional and dedicated engineer with demonstrated ability for building elegant and efficient solutions. You will be part of an international team in a rapidly growing company set for global expansion. This is a unique opportunity to join early and grow with the company.
Required Expertise/Experience
Professional software development experience (5+ years)
Relevant Android and Linux software development experience
System architecture and Object Oriented design
Excellent verbal and written communication skills
Technical skills – Required
Experience building Android applications and/or subsystems
Strong experience in C/C++/Java programming
Development of kernel modules and/or system libraries
Android ROM development
Technical skills – Desired
Development of Linux device drivers
Hardware acceleration (e.g., Renderscript, OpenCL, OpenGL ES, Tegra, ARM)
Hardware integration (CMOS camera sensors, MIPI, I2C)
Image processing/analysis (preferably using OpenCV)
Education
Bachelor or higher in Computer Science or similar.
Apply
Submit resume and a cover letter to jobs(at)theeyetribe(dot)com and we will contact you ASAP.
Hello Everyone,
I have created this topic as a guide for everyone who are willing to purchase / purchased the new Moto 360. There has been a lot of criticism lately about the choice of processor for Moto 360 specifically when it comes to the 45nm fabrication and the processor being "old" when compared to today's standards. I personally feel that it was an exaggeration to say that the processor was incompetant. Furthermore, "being old" is very vague term when electronics is concerned, considering the fact that technology is advancing at a rapid pace and today's innovation is tommorrow's history.
However, I am not sure about why Motorola would choose to go with OMAP3 and I wouldn't speak for or against their decision. They have made their choice and it's not a bad one at all considering the fact that OMAP is a very popular platform especially with embedded systems. I had started my development hobby working with OMAP3 based device Samsung Galaxy SL I9003 and I am quite well versed with the technical aspects of the platform. I am sure many of you might not have heard about OMAP3 at all or even knew that it exists. Hence, I would like to dedicate this thread specially for OMAP3, and focus on several aspects like the development scope, contributions from TI, current kernel version, compatibility with latest versions of android, other OMAP3 devices which have substantial development, etc.
A little history
OMAP3 was first popular among Nokia devices, with Nokia N900 featuring OMAP3430. There has been sustantial development with Meego and Linux on N900 and there was great support for the device in upstream linux. The developer community for the device is still strong and the 3.16 linux kernel release includes support for N900 modem. Apart from that Nokia N9 was the first device to feature OMAP3630 and it had a functional Android port even when it ran Symbian by default. Althought it is an old platform, the openness of OMAP encouraged a lot of developers to keep developing for the devices.
Development Resources [Android]
Latest Kernel Version: 3.0.8
Kernel Source by Texas Instruments: http://omapzoom.org/?p=kernel/omap.git;a=shortlog;h=refs/heads/p-android-omap3-3.0
Userspace Libraries [CM11 Kitkat]: https://github.com/CyanogenMod/android_hardware_ti_omap3
Userspace Libraries include HWComposer, Camera, ION userspace, OMX (Audio and Video Decoders / Encoders)
Framework Support for OMAP3 [CM11 Kitkat]: https://github.com/cyanogenMod/android_frameworks_av/commits/cm-11.0?author=dhiru1602
Most of the above patches are for OMAP3 support and they enable proper usage of the Audio and Video encoders and decoders.
Proprietary Stuff: The PVR-SGX530 driver is currently proprietary with binaries available which are fully compatible with 3.0.8 kernel. These binaries have proper support for asynchornous v-sync (Project Butter).
CM11, NamlessROM, Omni and all the other android distributions offically have support for OMAP3 on Kitkat. With several vendors refusing to release the source codes and not being developer friendly, it's often the biggest concern for an advanced user when choosing a device with a specific SOC. In case of OMAP3, you need not worry. :good:
Moto 360 Development Scope
From the above information, it's quite clear that OMAP3 doesn't lack development scope. However, the development ability on Moto 360 would be questionable. There are few questions that would need to look for the answers.
Kernel Version: At this point of time, it's unclear if Moto 360 uses an outdated 2.6 kernel or latest 3.0 kernel. Android on OMAP3 would require 3.0 kernel for proper compatibility between the GPU, Display Subsystem (DSS) and DSSCOMP (Composition Pipeline). However, Moto could have used a custom 3.4 kernel just like Google did for Google Glass that runs on OMAP4. Most of the OMAP3 code for 3.0 kernel is based on OMAP4. Probably someone could use ADB over Bluetooth and confirm the kernel version for us.
Serial / USB Connection: Lack of Serial / USB connection would make it hard for development since a brick would prove costly. It's hard to comment on this right now since we need to explore more.
Android Wear: As of now it's unclear as to what Android Wear has to offer for OMAP3. The support for OMAP3 was being shed off more and more from upstream android with each release.
Locked Bootloader: There are probable chances that Moto 360 would come with a locked bootloader making it harder to run unsigned images. All of the Motorola OMAP3 devices are bootloader locked with no full unlock solution so far.
CPCAP: Motorola OMAP3 devices are known to use CPCAP Power Management Chip, which is a modified version of the generic TWL5030 present in all the other OMAP3 devices. This CPCAP chip has proved hard to work with and could be a problem for kernel hacking. Althought the iFixit Teardown Guide doesn't likely indicate the presence of CPCAP PMIC, but I might be wrong. Probably Motorola developers at XDA could give us some insights.
Contributions from Motorola: I have no idea how developer friendly would Motorola be when it comes to providing proper sources for the kernel and important userspace components if they decide to use a newer kernel which is not supported by any other OMAP3 device.
Other OMAP3 Devices on XDA
Motorola Defy, Motorola Defy+, Motorola Milestone 2
Stock Android Version: 2.3
Stock Kernel Version: 2.6.32
Community built Android Version: 4.4.4
Community built Kernel Version: 3.0.x
These devices are probably the most similar devices when it comes to Moto 360. Thanks to the contributions and hard work of @Quarx and others, who have managed to do wonders on CPCAP Bootloader locked Motorola devices. Their outstanding work had been showcased in the XDA Portal.
Samsung Galaxy SL I9003
Stock Android Version: 2.3
Stock Kernel Version: 2.6.35
Community built Android Version: 4.4.4
Community built Kernel Version: 3.0.101
This was the first OMAP device which was launched by Samsung. This device was subsequently replaced by the Galaxy Nexus. The latest version of Kitkat is available for this device and has also been featured in XDA Portal.
LG Optimus Black P970
Stock Android Version: 4.0.4
Stock Kernel Version: 3.0.8
Community built Android Version: 4.4.4
Community built Kernel Version: 3.0.101
This was the first device to receive official ICS build making use of the latest 3.0.8 kernel from OMAP. Thanks to the efforts of @Evisceration for his excellent work on this device which was very helpful for other devices as well.
B&N Nook Color
Stock Android Version: Ebook Reader.
Stock Kernel Version: 2.6.32
Community built Android Version: 4.4.4
Community built Kernel Version: 3.0.101
Nook Color is technically a Ebook Reader which was hacked and made to run Android. It's a WiFI only tablet running on OMAP3. It's officially supported by Cyanogenmod and CM11 Nightly builds are currently available. Thanks to the efforts of @fattire and @steven676 who maintain the CM11 builds for Nook.
Most of the device have 90% opensource binaries on the userspace and they don't have any major bugs. Thanks to the openness of OMAP3 which enabled us to make seamless kernel ports which worked flawlessly.
Since OMAP3 was the first platform that I worked with, it was a good learning experience for me provided most of the stuff was opensource and developer friendly. I am willing to extend my help for all the upcoming projects for the Moto 360. There are other developers who have contributed towards OMAP3 @Quarx, @fattire, @steven676, @Evisceration and many more who I am sure would surely be willing to contribute towards the development of this device.
Welcome to the OMAP World!
dhiru1602 said:
Locked Bootloader: There are probable chances that Moto 360 would come with a locked bootloader making it harder to run unsigned images. All of the Motorola OMAP3 devices are bootloader locked with no full unlock solution so far.
Click to expand...
Click to collapse
Thanks for taking the time to write this. Interesting and useful.
Actually, the MotoACTV has an unlocked bootloader by default and it runs on the same OMAP 3630 as the Moto360.
The MotoACTV also uses the same MSP430 dsp as a "sensor hub".
Here's plenty of tech info about the MotoACTV: http://wiki.opticaldelusion.org/wiki/Motoactv
dhiru1602 said:
Apart from that Nokia N9 was the first device to feature OMAP3630 and it had a functional Android port even when it ran Symbian by default.
Click to expand...
Click to collapse
Nokia N9 has got MeeGo operating system, not Symbian.
These are completely different OS-es.
mp107 said:
Nokia N9 has got MeeGo operating system, not Symbian.
These are completely different OS-es.
Click to expand...
Click to collapse
Also worth noting, MeeGo was Linux, that means it had an ARM Kernel, so not that hard to port Android for it aside from the upstream patches. Symbian was pretty much dead when the N9 came around.