▐▐ MISSION-HWA▐▐ aria

---

Wellcome to MISSION HWA


Why am I affected by?

Because you what CM9 and MIUI running on your phone.
But fast, smooth and with all functions or am I wrong?

About:

Wildfire S, Aria, Legend.. and more (you tell me) We all got the ports working on
your device. But without HWA it is unuseable. We are brothers and sisters, because our phones are similar.

CPU 600 MHz ARM 11
GPU Adreno 200


Why a mission?

You all are her because ONE PROBLEM needs to be solved.
Most things are fixed like WIFI/GPS/Network and so on.
Everyone love Android ICS but only a few run it because
its laggy, slow and not made for the daily use because of this bug.
And because I wanted a cool name^^

Most of the devices are running the CM7 Drowningchild Kernel.

We need to fix HWA. It enable a lot of apps for ICS and 3D but also the speed and smoothness.!


Working together is much successful than working alone.
Working harmonously together is much more enjoyable
And NOW START WORKING!

WE JUST NEED ONE WORKING KERNEL!! So we can port it and porting
a kernel isn't that hard.



GO TO THE THREAD
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Originally Posted by matt5eo

WE JUST NEED ONE WORKING KERNEL!! So we can port it and porting
a kernel isn't that hard.

Yes, it really is.

Originally Posted by matt5eo

WE JUST NEED ONE WORKING KERNEL!! So we can port it and porting
a kernel isn't that hard.

Drowning can do that !

Only kernel? What about egl... etc?

Here's the precise status:

There's a group of devices based on the msm-7x27 arch that all use the same adreno 200 driver. Their libegls will work for us, once we get a kernel updated to use the right gpu drivers. The problem is, the gpu drivers are all built around a later fork of the msm kernel tree, which is after the clock code was RADICALLY overhauled. This means our board files (arch/arm/mach-msm/board-liberty*) are not compatible with the new kernel trees, and the clock stuff+kgl stuff backporting to a kernel that works for us means integrating the clock changes.

I've been in communication with drowningchild on this, btw. He is not going to contradict what I say here.

'Just' porting the kernel over here means integrating a few THOUSAND lines of code from a different kernel, some of which are conflicting changes with what is in our kernel right now. The alternative (porting our board files to the new kernel) means porting THOUSANDS of lines of code to a kernel that is also partially incompatible, so it means re-writing a good chunk of it.

If you don't believe that I'm credible, here's the article discussing my port of the HTC Hero CDMA to kernel 2.6.35:

http://www.xda-developers.com/androi...-to-hero-cdma/

Let me know if I can help with anything...
(My kernel "skill" isn't very good though )

Originally Posted by s0be

Here's the precise status:

There's a group of devices based on the msm-7x27 arch that all use the same adreno 200 driver. Their libegls will work for us, once we get a kernel updated to use the right gpu drivers. The problem is, the gpu drivers are all built around a later fork of the msm kernel tree, which is after the clock code was RADICALLY overhauled. This means our board files (arch/arm/mach-msm/board-liberty*) are not compatible with the new kernel trees, and the clock stuff+kgl stuff backporting to a kernel that works for us means integrating the clock changes.

I've been in communication with drowningchild on this, btw. He is not going to contradict what I say here.

'Just' porting the kernel over here means integrating a few THOUSAND lines of code from a different kernel, some of which are conflicting changes with what is in our kernel right now. The alternative (porting our board files to the new kernel) means porting THOUSANDS of lines of code to a kernel that is also partially incompatible, so it means re-writing a good chunk of it.

If you don't believe that I'm credible, here's the article discussing my port of the HTC Hero CDMA to kernel 2.6.35:

http://www.xda-developers.com/androi...-to-hero-cdma/

Will it easier if porting a same processor device's kernel to our devices?
if i am not wrong , the sony X8 did have a same processor and it has HWA on ICS Port.

Originally Posted by zhuoyang

Will it easier if porting a same processor device's kernel to our devices?
if i am not wrong , the sony X8 did have a same processor and it has HWA on ICS Port.

It will be easiest from another HTC device, as they'll have a more similar code base. I believe the Wildfire S is the prime candidate. I'm on a Don Quixote-esque approach of grabbing the 3.0.8 msm kernel from code-aurora and am trying to just dump board files in and fix up the fallout. Currently merging the AMSS and SMD stuffs (still a long way from boot testing, in other words).

if a newer htc base is what we need what about the htc pico/explorer, based on 2.6.38?
i find the kernel version very odd for an android device, and the cpu (msm7225A) is labeled a scorpion?

Originally Posted by drowningchild

if a newer htc base is what we need what about the htc pico/explorer, based on 2.6.38?
i find the kernel version very odd for an android device, and the cpu (msm7225A) is labeled a scorpion?

Perhaps? Have a link to a recent tree for it? Ideally it'd be a 2.6.35 tree (not having to battle linux core changes is a huge plus), but 2.6.38 might not be bad. I believe 2.6.38 was the kernel standard for Honeycomb(could be completely off base), so it's likely that the chip was used in a tablet first, so a 2.6.38 kernel base was the standard (again complete smoke).