I don't know if this could help in developing better roms, but I found this on nVidia developer site: http://developer.nvidia.com/linux-tegra.
It seems they released the kernel 3.1 for Tegra...
CYA
Not very useful for android but it might be usefull for lilsteves ubuntu
Backporting their tegra-specific stuff from this source drop to the upstream sources for Android shouldn't be hard, but it would be a futile exercise since their closed-source drivers shipped with ICS would be 99% incompatible with the resulting kernel ABI (and those shipped with L4T won't work with the Android userland).
The only thing that give us a glimpse of hope is that they're dropping support for the obsolete Harmony reference design and instead they're focusing their efforts on Ventana (for Tegra-2) and Cardhu (for Tegra-3).
Related
This is a preemptive note about posting any new threads asking "when will honeycomb come to the gTablet?" or "why can't we do this because the Nook has it?" or "why isn't the sky blue today?"
Honeycomb is not available for the gTablet yet for the following reasons:
1. source hasn't even been released by Google yet
2. any port based on the SDK doth not a Honeycomb ROM make
3. we do not even have libraries (or source) from nVidia for Gingerbread yet
Until we have source from Google and nVidia, we won't have workable Honeycomb. There will be some ports, but until one of the above happens, we are not going to be getting Honeycomb. Best case is 30 days from now (roughly the end of March).
Any post asking about Honeycomb will be promptly closed and/or deleted.
This isn't about discouraging discussion about Honeycomb on the gTablet - it's about stopping the endless flaming and abuse and posting and complaining about something that has been answered multiple times - thus taking away from other progress and endeavors.
UPDATE 3/18/11 - We now have access to the Gingerbread libs needed for hardware acceleration, but in order to use them a complete rework of the github repo is required and a year's worth of merges and cleanups would need to be done. Slow going and no ETA.
UPDATE 4/12/11 - http://www.androidcentral.com/nvidia-stop-supporting-harmony-platform-past-froyo
UPDATE 4/13/11 - http://developer.nvidia.com/tegra/forum/honeycomb-harmony#comment-6191
UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
UPDATE 5/10/11 - There is now a pretty hacked together port of HC that has been ported to the gTablet - it is a mashup of other, authorized by Google tablets which have stock HC on them, and thrown together for Vega, Adam and gTablet. A lot doesn't work; it is not feature perfect..... it is only recommended for testing type users who are familiar with nvflash etc. and it is not built from source specifically for our devices. It is by no means official, nor is it what would probably be called "stable" - but it is as close as we've come to HC on the gTablet. Here is the post that has more information: http://forum.xda-developers.com/showthread.php?t=1065220
UPDATE 5/10/11 - Per Google I/O's Fireside chat today there will be no Honeycomb source released. Ever. You'll have to wait for Ice Cream Sandwich which will be out in Q4 2011.
UPDATE 5/14/11 - The ADAM/VEGA/ZPAD/GTAB port of the mashup Transformer/Iconia/Xoom Honeycomb systems is coming along nicely. See the above thread for more information. Good work to the devs involved in that project.
I just got my Adam on Friday, and have been enjoying it without having done anything too hackish to it yet (thanks largely in part to the Amazon appstore).
I'm not really sold on the Eden UI system yet - it still feels a little bit buggy and not fully baked to me, but it may have potential. But if it were open source, any of us could work to improve it, and I do remember it being mentioned on the blog that the NI software would be open sourced (correct me if I'm wrong, hard to understand precisely what is meant sometimes).
notionink.wordpress.com/2011/01/28/more-updates (can't post outside links as a new member)
Source for other Notion Ink’s Application: If you are looking for the code for any specific apps on the Adam, you can directly write to developers at notionink dot com and they will add you in the priority list! All the softwares developed by Notion Ink are open source and will be shared with the community soon. As far as the SDK goes, we are migrating from 2.2-2.3 to Honeycomb and once the platform is stable, will be shared with the developers.
Click to expand...
Click to collapse
Given that the Honeycomb source isn't to be released any time soon, I'm curious what people's opinions are about whether Eden/NI software could make a viable open-source alternative to Honeycomb?
Would you prefer an open-source Eden/Froyo/Gingerbread rom over a Honeycomb rom (if the Honeycomb source is closed)?
Or would you rater drop Eden and stick to Android roms? (whether they be Honeycomb or not)
Would you like to see Eden ported over to more tablets? (which may or may not support Honeycomb any time soon) Do you think it could be an effective Honeycomb alternative for other tablets?
EDIT: Had to shorten the poll answers, here's what I'm asking:
Honeycomb, even if it can't be rooted/customized - you just want Honeycomb at all costs and don't care about its hack potential
Honeycomb, rooted and customized - you want Honeycomb, but only if it can be effectively hacked/customized
I'd rather stick to an Eden/AOSP-based system - you want maximum flexibility and see Eden/latest android source as a viable alternative, or may be a purist in terms of open source
Drop Eden, latest open-source Android - you don't care for Eden, but do want your system open source
At the moment Eden sucks and gives no added value in my opinion.
Nevertheless I would like to see a Honeycomb Eden version.
If I should choose right here and know I would choose Honeycomb (and of course it can be customized and rooted - its a bit foolish to think that this will not happen...)
@rolliradi8 : +1
I really don't like eden, loving Beast or VEGAn ROMs thought..
But honeycomb would be super awesome!
Allthough I am also really excited for trying Mad Murdock's CM7 ROM..
As it appears they have had either a change of heart or the community is large enough to have a voice..
Mar 16 2011 at 12:07 AM #1
UPDATE 13 APRIL 2011
A lot has been read into a very short post about a Tegra development kit. I'd like to clear up a few points.
First, nothing changes in what we’re delivering to the open source community or customers. NVIDIA will continue to post the Tegra kernel to kernel.org and publish our Android code to our public git servers. Additionally, we will continue to make our BSP (codecs, GPU driver etc) available to all our hardware partners. We will continue to do this and nothing about these processes has changed.
For our partners' Android devices, NVIDIA provides support until the hardware partner chooses to no longer support the device. So, for instance, NVIDIA will support the Xoom on all versions of Android Motorola requests until Motorola ceases to support the Xoom. The same goes for ViewSonic with the G-Tablet, Notion Ink with the Adam, Acer with the Iconia, LG with the Optimus 2X and so on.
In relation to my original reply, that was a response to a specific question about a Tegra 250 Development Kit. Given the confusion, we will work with owners of Tegra 250 Development Kits individually to determine their needs. The term "Harmony" is an internal codename for the Tegra 250 Development Kit. It is not a tablet reference design. Each shipping tablet is a custom design with varying hardware components and requires a custom OS image from the OEM who made the tablet.
Finally, while we cannot support or give out third party peripheral drivers or provide the Android 3.0 source before Google does, we do want to explore whether we can assist the open source ROM makers. We will be reaching out to them today.
UPDATE 12 APRIL 2011:
Sorry folks looks like I caused a bit of confusion. Since this is a developer forum my comments
were targeted at Tegra Honeycomb developers and for this we’d like to focus on Ventana. For shipping or production products, customers should contact the device makers directly for OS support plans. They are responsible for the OS shipping on their device.
In relation to our linux kernel git repository, NVIDIA will continue to provide full open-source support for all of our kernel components and will push more of that upstream over time.
ORIGINAL 16 MARCH 2011:
NVIDIA is only supporting the Ventana platform for android releases going forward. At the moment we have released Froyo and Gingerbread OS images for Ventana and will release Honeycomb after Google has done so.
Andrew Edelsten
Tegra Developer Relations
NVIDIA Corporation
SOURCE(s):
http://developer.nvidia.com/tegra/forum/honeycomb-harmony
http://notioninkhacks.com/index.php/2011/04/12/huge-problem-on-the-honeycomb-front/
http://conclave.notionink.com/showt...mb-on-Harmony-NVIDIA-s-Official-Stance&p=1281
Quoted from Engadget:
The latest refresh of the Linux kernel, 3.3, is now available, and the second release of 2012 brings with it the long-awaited merging of code from Google's little side project. While that is particularly interesting to developers looking to boot Android or run apps on the stock Linux kernel (FYI: optimized power management and other infrastructure that didn't make it this time will arrive in the next release, 3.4) and represents a resolution to the issues that kept the two apart for so long it's not the only new feature included. There are improvements to file systems like Btrfs, memory management, networking, security and much, much more. Hit the source link below for the full changelog or grab the code and from the usual locations and get your compile on directly.
Source: Engadget, Kernel Newbies, LKML.org
Any devs interested in developing a kernel based on this?
Based on what I read, this release would make it easier for us to compile the kernel as it brings merged Android code.
To me I'm thinking Google will Roll this out to the Nexus Line Up on the Next OTA... Perhaps the delay for the Nexus S if Due To This?
- Google
nice I hope so
iGoogleNexus said:
To me I'm thinking Google will Roll this out to the Nexus Line Up on the Next OTA... Perhaps the delay for the Nexus S if Due To This?
- Google
Click to expand...
Click to collapse
I doubt this is due to any delays regarding ota update, AFAIK, the Android devs at Google have all their own modules etc that they roll in to an update etc. This should however make projects like Ubuntu on Android etc easier.
Sent from my A500 using xda premium
glennkaonang said:
Quoted from Engadget:
The latest refresh of the Linux kernel, 3.3, is now available, and the second release of 2012 brings with it the long-awaited merging of code from Google's little side project. While that is particularly interesting to developers looking to boot Android or run apps on the stock Linux kernel (FYI: optimized power management and other infrastructure that didn't make it this time will arrive in the next release, 3.4) and represents a resolution to the issues that kept the two apart for so long it's not the only new feature included. There are improvements to file systems like Btrfs, memory management, networking, security and much, much more. Hit the source link below for the full changelog or grab the code and from the usual locations and get your compile on directly.
Source: Engadget, Kernel Newbies, LKML.org
Any devs interested in developing a kernel based on this?
Based on what I read, this release would make it easier for us to compile the kernel as it brings merged Android code.
Click to expand...
Click to collapse
I have been porting Samsung drivers for Nexus S for some time till Linux 3.3 RC3..
Sorry, no fully working results yet due to many code improvements..
But the work is in progress.. I'll also try to write so Samsung to get the info about their plans and/or the results of porting this code to 3.3
novic_dev said:
I have been porting Samsung drivers for Nexus S for some time till Linux 3.3 RC3..
Sorry, no fully working results yet due to many code improvements..
But the work is in progress.. I'll also try to write so Samsung to get the info about their plans and/or the results of porting this code to 3.3
Click to expand...
Click to collapse
Thanks for your hard work, man.
Anyway, after some readings, I think it's better for us to wait until 3.4 is released.
It is said that 3.4 will finish all the Android code merging process, with many fixes of course.
I'm no dev at all, so this is just a plain opinion from somewhat avid Android user
Sent from my Nexus S using xda premium
Cool
XBMC will soon be the driving force for people looking to purchase Android TV devices. The Android TV community however, is seriously lacking in the ROM department for Android TV sticks and set top boxes. If you're a reputable developer and interested in getting involved in this new, exciting and soon to be huge community which is the Android TV community here at XDA, get with me and I'll make sure you get the hardware and information you need.
Cheers!
Can elobrate more.
Hope to help.
Have MK808
Basically I'm trying to get a team together of people experienced in Android TV Sticks so that we can make proper documentation and perhaps create better ROM firmware files for them. I have many resources and hardware to share. Just get in touch at my site.
XBMC ANDROID said:
Basically I'm trying to get a team together of people experienced in Android TV Sticks so that we can make proper documentation and perhaps create better ROM firmware files for them. I have many resources and hardware to share. Just get in touch at my site.
Click to expand...
Click to collapse
What you need to get proper development on these is some proper kernel sources for Rockchip processors... The RK3066 "sources" are incomplete, and use "blobbed" .o files rather than including the c sources for some parts.
While I've been working on CM10 with some another guy, this is a fairly big nuisance.
The MTD driver is blobbed, and very badly broken... Needing lots of workarounds to just make it work.
There's limitations to what is possible, but some decent kernel sources would be the first thing. The actual building and booting of the kernels is less of an issue now we've got that figured out.
Devolpers rk3066
Here u have some intresstering links for rk3066 devices.
[/COLOR]Ubuntu for rk3066 devices:
http://code.google.com/p/rk3066-linux/
First linux webserver running on a rk3066 device
http://ubuntu.g8.net/
Source code:
http://service.i-onik.de/
extra.
http://odroid.foros-phpbb.com/t2051-working-mali-400-opengl-es-acceleration