Atrix + (Xoom kernel + Libs)

[mvniekerk]

Both are Tegra2 devices
Both are using the same Wifi chips
Both are GSM/HSPA devices

Plan of action:

1. Get Xoom kernel for 2.6.32 (same level as the kernel we've got for Atrix)
2. Diff the two for platform specific changes
3. Get Xoom kernel for 4.1.2 release (http://www.xda-developers.com/android/motorola-xoom-gets-stock-rooted-android-4-1-2/)
4. Put in platform specific changes learned from diff

Then you should have a binary compatible Atrix-fied Xoom kernel, running on the Atrix. Which enables you to

1. Use Xoom hardware acceleration
2. Have a propper Project Butter experience
3. Have a kernel that doesn't run on the compatibility mode of bionic libraries
4. A more modern and mature Linux kernel (and libs)

Xoom Device specifics
git clone https://android.googlesource.com/device/moto/stingray
Xoom Kernel
git clone https://android.googlesource.com/kernel/tegra
Xoom Sourceforge page
http://sourceforge.net/projects/xoom.motorola/files/
Wiki entry for the SOC
http://en.wikipedia.org/wiki/Tegra (note the difference, we're using Ventana, Xoom is using Harmony => we are using different chips - surprise...)

board-*.c differences

ATRIX STARTUP (tegra_olympus_init)

• Tegra common init
• Programming jig on GPIO PV6 disable
• Pin multiplexing
• Clock init
• Setup debug UART on UART B
• Start DSI clock
• Start 3D clock, make sure it is at correct speed
• Register platform devices
• Keypad
• I2C
• LCD Panel
• SDHCI/MMC
• WLAN

Nothing weird here.

XOOM STARTUP

• Tegra common init
• Tegra init suspend
• EMC
• Setup Tap delay on wifi chip to 6
• Programming jig on GPIO PV4 disable
• USB OTG setup
• Setup GPIO for charging circuitry on GPIO PV5
• Enable charge LEDS
• Dynamic voltage and frequency scaling disabling on P1 hardware
• Enable power rail on Wifi/BT chip BCM4329
• Pin mux edit
• Clock init
• Setup debug through UART B (! same as Atrix)
• Init Digital->Audio converter 1
• Init Digital->Audio converter 2
• Setup device structs on platform struct
• Audio init
• RAM Console start
• Weird memory carve outs (for what, firmware later on?)
• Register platform devices with kernel
• I2C
• Power off (?) init
• Keypad
• Touch
• Power
• W1
• WLAN
• GPS
• USB
  Marked are things that are different and / or weird in the init phase.
  

 

[anaschillin]

Its a good plan, but woudnt the architecture be slightly different?

 

[mateusdalpi]

I really don't know what it means, but it was said very often in the forums:
Xoom = SoC T20
Atrix = SoC AP20h

But I hope that you can do some magic :silly:

 

[damonsmith666]

Have you actually started this process or is it just a plan you hope will work?

Sent from my MB860 using xda premium

 

[peddarson]

it's not only the cpu and antenna...there is also the camera,fingerprint and imo the resolution of the screen is also important...

so this kernel cannot be used...only some parts of it mabe

 

[kkuuo]

If is works, It will be a great dev but
is it possible?

Sent from my MB860 using xda app-developers app

 

[mvniekerk]

Also, code names for these units:
Xoom = Stingray
Atrix = Olympus

https://android.googlesource.com/kernel/tegra/

Found the kernel source... Seems as though we are capped at 2.6.39, for now.

I really don't know what it means, but it was said very often in the forums:
Xoom = SoC T20
Atrix = SoC AP20h

But I hope that you can do some magic :silly:

 

[fabianowerner]

Can you point me up on what does that mean?

Sent from my MB860 using xda app-developers app

 

[Newbleeto]

Finally someone that's thinking in the long term. Barring a kernel source leak from Motorola, this would be a way to go. Sounds like massive coding process though. Are you up to it? Do you have a plan?
Kudos for the idea.

 

[nvboza]

I have XOOM MZ601, because of that I buy Atrix, it's the same machine...this will be great, and also tu put webtop ( I know I am boring, but I have lapdock and I desperately need webtop ):good:

 

[mvniekerk]

Finally someone that's thinking in the long term. Barring a kernel source leak from Motorola, this would be a way to go. Sounds like massive coding process though. Are you up to it? Do you have a plan?
Kudos for the idea.

Ok - some history:
I've worked at a mining communications/safety company Becker Mining Systems, for their R&D firm Becker R&D in South Africa.
We've developed an Android VOIP phone for to be used in mining (hazardous, please-don't-make-a-spark) environments. We've succeded, but then Germany practically canned their colleries (hug-a-tree-don't-kill-johnny-polar-bear) - resulting us to stop development 2 months before manufacturing (literally only had to make the moulds). Sigh - the collery overseers DSK was the contracting client.

My job was to get Android running on this Freescale iMX31 based platform. I did the kernel + Wifi + Android + VOIP and a bit of the UI.

Plan of action:

• /arch/arm/ is the first point to go looking for things in the kernel. In this case, we'll be looking for /arch/arm/mach-tegra/, this is where all the platform specifics will hide away.
• Compare board-olympus.c and board-stingray.c (+ board-olympus.h and board-stingray.h). Look for similarities, look for differences. These are the glue points - in this .c files the startup / fixup / powerup of the platform starts off. See it as the void main(void) file for the platforms.
• Adapt the board-stingray.c in such a way that it starts up on the Atrix
• After kernel start up, get the peripherals running. This includes UARTS (USB the most common, and debug), SPI (chats to other peripherals), MMC (chats to the WiFi/BT module) and also the screen.
• Merge in libraries - we'll probably using the Atrix radio driver file, but the rest (Wifi, OpenGL libs) from the Xoom

If all of this doesn't make sense to you, please press the thank you button and refrain from commenting on this feed

 

[ivica86]

Hmmm... yeah you are the right person for this job :laugh::good: :highfive:

 

[Manzing]

I wish you to succeed, you would make lot of people to be really happy !
If you need testers, i'll be right there.

 

[djluis48]

Jokersax already said its possible, in fact, he was using some Xoom binaries that he ported, but he also said that it required a MASSIVE amount of coding, time and skills to get it done.

Hope you can accomplish this dude! Good luck!

 

[djluis48]

yeah well those didn't really make a difference... and we have the libs, only need a supporting kernel.

Indeed, he showed that it was possible.

 

[lehjr]

It might help when nVidia goes opensource with the Tegra drivers, but so far I haven't seen enough details on that to be encouraged yet. I suspect that what we'll see will be either code dropped into nouveau or a separate driver set rather than nVidia opening up their proprietary drivers.

 

[Zeljko1234]

mvniekerk, please join Atrix Re-Birth Project.

We already have libs for Atrix, two leaked rom, closed kernel, useful CM 10 (I'm using it right now), great developers (Epinter, MMontuori, TPoint75...)

With your knowledge and enthusiasm we could go even further and faster.

 

[mmontuori]

This can be tested, it's very simple, dd the xoom boot partition to a file, then flash out back to the Atrix. If it passes the boot logo, there is hope...

Sent from my MB860 using xda app-developers app

 

[cpl101]

mvniekerk: If you're serious about this undertaking, I'm sure there would be quite a few willing to donate, including myself.

 

[marcovrv]

In fact, I suggested something similar, but using the Galaxy R kernel as base ( http://forum.xda-developers.com/showthread.php?p=32274673, last post on that page). That is a 3.x kernel.

Sent from my MB860 using xda app-developers app