Information is slowly trickling out about upcoming partnerships and hardware (phones/tabs) that will be using the Tegra 3.
Will Unity Android fully support this crazy new hardware?
It’s looking to be a quad core, 1.5ghz processor, the new 12-core Nvidia GPU with support for 3D stereo. Tegra 3 will support a new form of High Definition called Extreme HD which has a resolution of 2560 X 1600.
I’m excited about the games we’ll be able to make for these devices, needless to say. 
Unity does not even fully support Tegra2, so I would wait with this question until more is known about the hardware and upcomming multithreading support at all.
Also, that are theoretical data. NVIDIA, like ATI, were too long in the gpu game to be able to claim real world data. For example they claimed a lot for tegra2 but kind of “forgot” that their architecture sucks with fixed type shader units which makes it hell less flexible than all the competition - the only reason tegra2 is fine is cause its available in masses nowadays and recently after LGs total flop with the xoom tablet (not even reaching 10% of the expected sales and endangering LG seriously on that business branch), its prices seem to have been dropped into a realistic range too.
so we better wait and see what it really will offer and especially when, how android will work with it if at all and in what shape unity is by then multithreading and multi gpu wise.
What do you mean exactly?
btw multi-threaded support on ios/android is coming with 3.4 - so skinning will be offloaded.
Also we are working on bringing even more multithreading 
With that I mean in detail that at the time, the second core is widely running basically idle unless you bomb it with WWW requests or async operations.
Looking forward to what 3.4 will bring to support multithreading as in no longer brinking Invokes which would normally offload to a thread pool and Unity being thread safe so we can savely offload path finding and other cpu intense but “runs widely on its own but requires some data which are unreasonable to clone all the time” for example which at the time isn’t possible without data cloning which again is a problem on mobiles due to performance, garbage collection and naturally RAM limitations.
Offloaded skinning naturally is nice especially for Androids with their lack of VFP - Neon requirement, but I wouldn’t put that on top of the “wants” list. Unbricking PhysX so it can run multithreaded, audio playback offloading and similar things is much more important out of my view as they are of global importance in the game, not just of importance for 7 animated objects …
What I naturally hope to see on the threading end in a future 3.x version is finally streaming support.
right now there isn’t one, cause streaming scenes are useless in those cases where you want to use them to replicate streaming as umbra doesn’t stream, the same limitation exists for standalone scene bundles and asset bundles can’t transfer umbra at all etc so larger worlds which rely on streaming are technically impossible, more sophisticated mobile worlds suffer from the same due to the memory limitations which would require streaming to be handled and on Windows its even worse with the Umbra Process 2GB border which does not even allow empty bumpy terrains to bake PVS at all.
I’m eager to see the future though as you guys did a great job normally and the targeting of XBox 360 should definitely have helped on that end too with its “be multithread or die” cpu architecture
Thanks for chiming in. I appreciate the information.
I agree. I think there are some other things that would be more important to have multithreaded, but you have to start somewhere, and in my current game it seems like skinning is a big chunk of the processor time. Offloading that to a separate core and giving everything else to the other would be a great improvement, I believe.
Also, did you mean the Motorola Xoom or the LG Optimus Tablet? The Motorola Xoom seems to be selling pretty well from what I understand. The Xoom 2 will possibly be using the Tegra 3, which is how I heard rumor of all this.
I do think you’re right that targeting consoles will be a great help towards adding multi-threaded support. It’s pretty essential on those platforms.
I meant the xoom, but naturally not LG, sorry.
Also such a flop could naturally not be a threat for LG, unlike Motorola which is on a whole different financial situation.
Selling “pretty well” is relative.
They projected 1M sold devices for the initial start month, the sales broke down at 100k devices and are staggering completely and it really brought Motorola into major trouble (unlike the Optimus X2 / Optimus Speed ones naturally which sold somewhere great but nowhere as much as HTC and Galaxy S spinoffs), which is to a fair degree Motorolas greed firing back as $1k with inexistant Android 3 applications, Androids eco system and naturally the simple fact that its just 3 tads too expensive compared with iPad prices + iOS ecosystem.
The Optimus x2 and upcoming Tegra2 devices like the Galaxy S2 I9103 are for me reasons to support an animation offload naturally, be it just due to what I mentioned above, the lack of guarantee for math coprocessor, which only half the 2 core cpus are offering at all (not the Tegras), but I’m not sure its the largest cpu hog on Android which could be offloaded.
As mentioned: looking forward whats going to happen, perhaps some of them help on my outdated HTC Desire to get more out of it 