Letting this die. New dev and user threads created.
- Thread starter Hashcode
- Start date
- Status
http://kernelnewbies.org/Linux_3.3?el
Summary: This release features as the most important change the merge of kernel code from the Android project. But there is more, it also includes support for a new architecture (TI C6X), much improved balancing and the ability to restripe between different RAID profiles in Btrfs, and several network improvements: a virtual switch implementation (Open vSwitch) designed for virtualization scenarios, a faster and more scalable alternative to the "bonding" driver, a configurable limit to the transmission queue of the network devices to fight bufferbloat, a network priority control group and per-cgroup TCP buffer limits. There are also many small features and new drivers and fixes are also available.
You didn't go far for now, maybe switch to new 3.3 kernel instead of 3.0?
Summary: This release features as the most important change the merge of kernel code from the Android project. But there is more, it also includes support for a new architecture (TI C6X), much improved balancing and the ability to restripe between different RAID profiles in Btrfs, and several network improvements: a virtual switch implementation (Open vSwitch) designed for virtualization scenarios, a faster and more scalable alternative to the "bonding" driver, a configurable limit to the transmission queue of the network devices to fight bufferbloat, a network priority control group and per-cgroup TCP buffer limits. There are also many small features and new drivers and fixes are also available.
You didn't go far for now, maybe switch to new 3.3 kernel instead of 3.0?
Wouldn't recommend switching to a new kernel willy-nilly when we don't even have a working 3.0.8 kernel yet. The 3.0.8 release that's being worked on is officially sanctioned for the motherboard. It really should be "new enough" for the time being.
But that is interesting news that Android and mainline Linux are finally going to start getting along.
Yes, troll-bait, but the above response was really funny!
Made the whole thing worthwhile. Thanks!
Agreed, for now I think we should stick with the Kernel that the board was built for...
Those features are nice, but many of them have no practical application in a Kindle Fire. (as of now) RAID striping just isn't something that can practically be done on our devices and most ROMs don't make any use of BTRFS anyways. (ext4/ext3 is fast enough and stable). The list goes on, but none of the new kernel additions seem to be all that relevant to the Kindle Fire environment.
That said, once we have the 3.0.8 running, I will whole-hardheartedly support forward movement.
Technically after merging in TI updates from the p-android-omap-3.0 branch, the Kindle Fire kernel is now at 3.0.21.
I was hitting some roadblocks with the mmc controller and some of the bugfixes / changes were very interesting looking. But anytime you merge code or make large changes, there are a few days of cleaning up merge issues, etc. Which is what I'm doing now.
Also, word from the NookTab guys was that if you could work out some driver / support issues, its actually easier to bring new devices up on a 3.2/3.3 kernel due to code cleanup and streamlined support for the architecture.
Someday maybe.
Sent from my XT894 using XDA
I was hitting some roadblocks with the mmc controller and some of the bugfixes / changes were very interesting looking. But anytime you merge code or make large changes, there are a few days of cleaning up merge issues, etc. Which is what I'm doing now.
Also, word from the NookTab guys was that if you could work out some driver / support issues, its actually easier to bring new devices up on a 3.2/3.3 kernel due to code cleanup and streamlined support for the architecture.
Someday maybe.
Sent from my XT894 using XDA
Had you read that post, you would notice that he is posting updated boot log on his blog:
http://blog.hash-of-codes.com/kindle-fire-ics/
As you can see, it is updated today, so he is working on it. Since no one else contribute to what he is doing, and he didn't came to some breakthrough since last post here, there is no point for him to post here.
http://blog.hash-of-codes.com/kindle-fire-ics/
As you can see, it is updated today, so he is working on it. Since no one else contribute to what he is doing, and he didn't came to some breakthrough since last post here, there is no point for him to post here.
Stop posting garbage.....
<rant>
Plz people....out of 90 some odd posts, there are about 5-8 worth reading. Can we all grow up and stop posting garbage??? We dont need every XDA member dropping in to post "I agree with .......whatever". All you do is waste space, and make these forums impossible to find the actual content people are looking for. 60 posts for troll bait...really??? Cant we just let Hash and the other devs to their thing and follow along without wasting server space with worthless posts? Flame away.....I really dont care.....but PLZ, PLZ, PLEASE stop wasting time and space.
</rant>
<rant>
Plz people....out of 90 some odd posts, there are about 5-8 worth reading. Can we all grow up and stop posting garbage??? We dont need every XDA member dropping in to post "I agree with .......whatever". All you do is waste space, and make these forums impossible to find the actual content people are looking for. 60 posts for troll bait...really??? Cant we just let Hash and the other devs to their thing and follow along without wasting server space with worthless posts? Flame away.....I really dont care.....but PLZ, PLZ, PLEASE stop wasting time and space.
</rant>
Yes, and complaining about those posts are another 40 posts to read
So... maybe just ignore posts with stupid questions and resp only to something constructive?
Quick Status update:
I completed the latest source code merge with TI's omapzoom and the kernel is now technically version 3.0.21 (as opposed to 3.0.8). During this merge I removed quite a bit of Amazon customization from the kernel sources and will continue to do so as needed, because it makes updates about a quadrillion times easier.
The bootup status really hasn't changed much: Kernel boots, init kicks off, the services startup and about the time we hit "surfaceflinger / bootanimation" the whole process stalls out.
A new change, is that ADB is now up and running and that's helping troubleshoot quite a bit. It means access to logcat, shell, etc. So far it looks like the halt is due to a 2.6 backlight driver and some framebuffer configuration issues. Hoping to make some progress on those soon.
Also, I've started the updated Android build under "ics-test" branches in the KFire-Android git for both device/amazon/otter and vendor/amazon/otter (https://github.com/KFire-Android). Here you can see what a "regular" ICS build for the Kindle Fire looks like. Almost all of the vendor files are removed (which came off the original device), and it has 3.0 kernel modules and board config. This includes removal of most of the legacy hacks that are used for OpenGL, old style Wifi config, etc.
I'll get you more info as it happens. But, you can trust that if nothing is being updated here or on the blog (http://blog.hash-of-codes.com/kindle-fire-ics/); it's not because I'm ignoring the KFire. I'm just not making much progress.
I completed the latest source code merge with TI's omapzoom and the kernel is now technically version 3.0.21 (as opposed to 3.0.8). During this merge I removed quite a bit of Amazon customization from the kernel sources and will continue to do so as needed, because it makes updates about a quadrillion times easier.
The bootup status really hasn't changed much: Kernel boots, init kicks off, the services startup and about the time we hit "surfaceflinger / bootanimation" the whole process stalls out.
A new change, is that ADB is now up and running and that's helping troubleshoot quite a bit. It means access to logcat, shell, etc. So far it looks like the halt is due to a 2.6 backlight driver and some framebuffer configuration issues. Hoping to make some progress on those soon.
Also, I've started the updated Android build under "ics-test" branches in the KFire-Android git for both device/amazon/otter and vendor/amazon/otter (https://github.com/KFire-Android). Here you can see what a "regular" ICS build for the Kindle Fire looks like. Almost all of the vendor files are removed (which came off the original device), and it has 3.0 kernel modules and board config. This includes removal of most of the legacy hacks that are used for OpenGL, old style Wifi config, etc.
I'll get you more info as it happens. But, you can trust that if nothing is being updated here or on the blog (http://blog.hash-of-codes.com/kindle-fire-ics/); it's not because I'm ignoring the KFire. I'm just not making much progress.
Working:
Currently Troubleshooting:
Future Changes Per Difficulty:
- Touchscreen Driver (Has been finicky but there is new untested driver source available)
- 127x Wifi Driver (Should work when we're ready to test, with normal expected troubleshooting)
- Sensor Driver Updates (Should work when we're ready to test, with normal expected troubleshooting)
- HW Acceleration Testing (If backlight and graphics timer issues are solved correctly, this should work, with normal expected troubleshooting)
- Audio Source / Driver Update (Need userspace ICS source update for AIC3110 codec to really do audio the "right" way, vs. janky legacy method we're using now)
Awesome hashcode!! Keep up the good work man!
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
229LAST UPDATED: 4/2/2012
WHERE ARE WE NOW? IS IT BOOTING? CAN I GET A NEW ROM W/ AN ICS KERNEL?
Is it booting? Yes.
Is there a new ROM for the kernel? Yes. It's still a work in progress and likely to continue changing as the kernel gets more developed.
Can I test the new ROM? Right now, there's no reason to run this ROM unless you're working on the kernel and/or bug testing. It is booting into the OS now and as soon as I fix up the Wifi and SD MMC mount, I'll probably put up a test link for testers -- lots to bugfix, this isn't "usable" yet. Especially since we don't have the Ducati loading for hw codecs.
How long will it take to fix? There is no way to know. I work on the kernel about 4-5 nights a week, and when I fix something, there's always something behind it which needs fixing as well. I am making good progress (in my opinion), but that may still mean weeks of development.
I'm going to keep a page updated on my blog so that at any point in time if you're curious what the output of the boot up looks like you can go take a look (this will be mostly technical output and don't worry if it much of it doesn't make sense):
http://blog.hash-of-codes.com/kindle-fire-ics/
[NOTE: I've now highlighted items in green which are good and some red items still to be fixed.]
2nd post has the current status in more detail134UPDATED 4/7
WORKING -- WILL NEED TESTING:
EXT4 MMC Filesystem Access
USB Android Gadget with modes like ADB and MTP (Do we want mass storage also?)
Battery / Charger Driver
Display driver / SGX / ION now plays nice w/ 512M memory (originally the 3.0 kernel was hard coded for 1G of memory)
Touchscreen is working
Sensors are working to detect tilt / movement
Power button working (no colored leds yet)
New Audio driver from TI is working (thanks nook_lover!)
Headset output / recording
Internal media partition mount
Ducati binary is being loading by the system now and the OMX server is starting -- NEEDS TESTING -- probably still won't work -- but its progress towards hardware codecs
PARTIALLY WORKING:
New Backlight Driver is now partially working. Won't adjust brightness yet, but it's coming.
:| Wireless device and driver is being recognized. Still troubleshooting.
STILL BROKEN:
:/ Color Changing Power Button Leds - Old Driver needs to be updated
FUTURE CHANGES IF NECESSARY:
- Touchscreen Driver has a newer straight Linux driver available which would need minor Android customization (current driver seems ok for now)
- Charger Driver has a newer straight Linux driver available which could be customized for Android (will probably do this one eventually. The current charger driver is very messy)
- Battery Gauge has a generic 3.0 android driver available. It would need minor customization (may or may not rewrite this one eventually)72Updated #2 post with some fixed items:
- Audio is now working, including headset jack for output and recording. (Thanks nook_lover for getting source from TI!)
- Internal "media" mounting is fixed
- Wireless drivers and modules are built but hitting an error in the OS. Troubleshooting this.
- New memory routines for handling our lower (512M) system in ICS are now working. I show 130MB free when I first boot up, and the system should dynamically allocate needed resources for the ION driver vs. The pre-allocated 200MB method that is used on 1GB systems.
I managed to get the Archos ducati binary to load and the OMX server to start. Now I want to be very clear: this is very experimental and probably wont work right off the bat. BUT it's progress on the hardware codecs front.
Once the wireless issues are ironed out, I'll crank up a new dev/testing thread with a CM9 v0.1 ICS ROM (running the new kernel).
Some quick notes about the upcoming testing:
- We'll actually have 2 threads: 1 here in the dev section for testers and devs to talk about current issues. And a 2nd "users" thread (not that the ROM should be used as a daily yet -- its not ready) in the general section. This should be where discussion about non-dev questions and/or tech support can happen.
- No ETAs. This is still a work in progress and fixes happen as they happen.
- Expect things to work, and then not to work, and then get fixed again.
Hope you're all enjoying your Saturday!
Sent from my DROID4 using XDA57I built Hash's kernel from source and integrated with AOKP build 30. It boots nicely and even fixed the static wallpaper. Obviously, no wifi yet as mentioned in his progress. Haven't tried much else, as I did this late last night and have to work now.
Awesome Hash, i'm learning from your hard work. Please don't bother him about this or keep asking for a test rom. If you really want one, it's not hard to build yourself.
Pyrotek, this is awesome And EXACTLY the reason I'm trying to keep the new build for Kindle Fire ICS as clean as possible. We should be able to bring up the more developed AOSP-based ROMs in a day w/o little to no customisation (AOSP, CM9, AOKP, etc).
Wifi is coming. I'm down to about 1-2 issues of debugging.
Side note: My work has been VERY busy over the last few days so I'm trying to get time in when I can, to get this out for testing.
Thanks for the patience.54Quick Status update:
I completed the latest source code merge with TI's omapzoom and the kernel is now technically version 3.0.21 (as opposed to 3.0.8). During this merge I removed quite a bit of Amazon customization from the kernel sources and will continue to do so as needed, because it makes updates about a quadrillion times easier.
The bootup status really hasn't changed much: Kernel boots, init kicks off, the services startup and about the time we hit "surfaceflinger / bootanimation" the whole process stalls out.
A new change, is that ADB is now up and running and that's helping troubleshoot quite a bit. It means access to logcat, shell, etc. So far it looks like the halt is due to a 2.6 backlight driver and some framebuffer configuration issues. Hoping to make some progress on those soon.
Also, I've started the updated Android build under "ics-test" branches in the KFire-Android git for both device/amazon/otter and vendor/amazon/otter (https://github.com/KFire-Android). Here you can see what a "regular" ICS build for the Kindle Fire looks like. Almost all of the vendor files are removed (which came off the original device), and it has 3.0 kernel modules and board config. This includes removal of most of the legacy hacks that are used for OpenGL, old style Wifi config, etc.
I'll get you more info as it happens. But, you can trust that if nothing is being updated here or on the blog (http://blog.hash-of-codes.com/kindle-fire-ics/); it's not because I'm ignoring the KFire. I'm just not making much progress.
