Hi to all Broadcom BCM215XX armv6 devices running android!
I'm glad to announce that, our organisation, BroadcomCM will start working on the port of AOSP ICS drivers for our CPU and GPU, BCM21553. First of all, I've asked moderators to close all my threads, why? We know we have [GENERAL] Thread for our projects but most users don't care, so this will be the thread to talk about it, development!.
Samsung stopped the development on this devices long ago, but their drivers where not ever released. Thanks to our petition, we have managed to force Broadcom to release the drivers, and we managed to release them on ICS, android 4.0+, way!
A bit of introduction:
Broadcom gave to us test driver builds, which were prebuilt, .so libraries, and we could not edit them, but they gave us the code to patch framework to make those prebuilt libraries work with our AOSP project (by that time, CyanogenMod 7.2). After some re-search and lot of work on our team (thanks Legolas93), I managed to implement AOSP Alcatel drivers to our CyanogenMod 7.2 Based ROM. This was the biggest change ever happened to that device, as we managed to fix 100% HW and as a cosnequence, libstatgefright was fixed too, and HGL. This resulted on camera/vide recordi (media profiles, encoding and decoding) to work, this was RC1. REMEMBER: As we extracted this libs from sotck AOSP alcatel ROM they are prebuilt, so we can not modify them at all.
SInce that moment, project on HW was stopped, and we focused to fix other issues not releted to HW (ext4, backlight, led, tethering, BT...), and we managed (most of them), and everyone enjoys now a CM, AOSP and Cyanmobile port brought to you by broadcomCM.
What else?
Broadcom released, or seemed to, BCM21553 driver source for AOSP ICS source. They released the source, so now we can know how our chip work. What is weird about it, is that this chip is released for ICS source, when it is an armv6 chip, and any device of our family has official ICS. (Maybe BROADCOM are really nice people, or maybe they trolled us). We will add new tag to be defined on Boardconfig.mk to make the drivers work on it.
So.. We did it?
Yes, we forced Broadcom to release the source, you, we, we all did this possible, and we should be prud of ourselves.
Will with this come BroadcomCM to develop?
Well, yes and no, we already have some surpises for BroadcomCM ROMs owner, which were not reletated to drivers at all, and they affect all devices. As this work is nearly finished (first alpha), we will release this next week, and then we will start working on it. Keep calm, good things make people wait for it don't ?
What is now?
Now, nice question. We will implement this source code on our CM9, ICS, branch. (all sources can be found on our github), and implement them on the build, will that be easy? OF COURSE NOT. Broadcom trolled us with first test builds of drivers, so maybe expect the same from that sources, we don't know and we will not know unitl we build it, and we have to compare each file, ONE PER ONE, so it will be a hard work.
Frequently asked questions can be found on the second post, as well as a video to show you what was having a device with drivers, and what was not. (Qualcomm vs Broadcom [armv6]).
I'm glad to announce that, our organisation, BroadcomCM will start working on the port of AOSP ICS drivers for our CPU and GPU, BCM21553. First of all, I've asked moderators to close all my threads, why? We know we have [GENERAL] Thread for our projects but most users don't care, so this will be the thread to talk about it, development!.
Samsung stopped the development on this devices long ago, but their drivers where not ever released. Thanks to our petition, we have managed to force Broadcom to release the drivers, and we managed to release them on ICS, android 4.0+, way!
Index:
Post 1 (this) ...................................... Information about drivers
Post 2 .............................................. Frequently asked questions
Post 3 .............................................. Drivers on Github (Opensource)
Post 4 .............................................. Videos showing HW working
A bit of introduction:
Broadcom gave to us test driver builds, which were prebuilt, .so libraries, and we could not edit them, but they gave us the code to patch framework to make those prebuilt libraries work with our AOSP project (by that time, CyanogenMod 7.2). After some re-search and lot of work on our team (thanks Legolas93), I managed to implement AOSP Alcatel drivers to our CyanogenMod 7.2 Based ROM. This was the biggest change ever happened to that device, as we managed to fix 100% HW and as a cosnequence, libstatgefright was fixed too, and HGL. This resulted on camera/vide recordi (media profiles, encoding and decoding) to work, this was RC1. REMEMBER: As we extracted this libs from sotck AOSP alcatel ROM they are prebuilt, so we can not modify them at all.
SInce that moment, project on HW was stopped, and we focused to fix other issues not releted to HW (ext4, backlight, led, tethering, BT...), and we managed (most of them), and everyone enjoys now a CM, AOSP and Cyanmobile port brought to you by broadcomCM.
What else?
Broadcom released, or seemed to, BCM21553 driver source for AOSP ICS source. They released the source, so now we can know how our chip work. What is weird about it, is that this chip is released for ICS source, when it is an armv6 chip, and any device of our family has official ICS. (Maybe BROADCOM are really nice people, or maybe they trolled us). We will add new tag to be defined on Boardconfig.mk to make the drivers work on it.
So.. We did it?
Yes, we forced Broadcom to release the source, you, we, we all did this possible, and we should be prud of ourselves.
Will with this come BroadcomCM to develop?
Well, yes and no, we already have some surpises for BroadcomCM ROMs owner, which were not reletated to drivers at all, and they affect all devices. As this work is nearly finished (first alpha), we will release this next week, and then we will start working on it. Keep calm, good things make people wait for it don't ?
What is now?
Now, nice question. We will implement this source code on our CM9, ICS, branch. (all sources can be found on our github), and implement them on the build, will that be easy? OF COURSE NOT. Broadcom trolled us with first test builds of drivers, so maybe expect the same from that sources, we don't know and we will not know unitl we build it, and we have to compare each file, ONE PER ONE, so it will be a hard work.
Frequently asked questions can be found on the second post, as well as a video to show you what was having a device with drivers, and what was not. (Qualcomm vs Broadcom [armv6]).
Last edited: