i9300 Galaxy S3 ArchiKernel V1.2 AOSP/Samsung/ArchiPort

Başlatan Fuul oyun, 12 Nisan 2016, 14:21:18

« önceki - sonraki »

0 Üyeler ve 1 Ziyaretçi konuyu incelemekte.


                        
Kernel Özellikleri
   Samsung Update13 Sources (NOT smdk4x12)
   Linux 3.0.101
   Compiled using Linaro 4.9.1 arm-eabi
   ArchiDroid Optimizations
   Using AnyKernel method (compatible with all ROMs for both AOSP and Samsung)
   ZZmoove 0.9 beta2 (as default CPU governor with moderate preset)
   Other CPU governors: PegasusQ, LulzactiveQ, Performance
   ROW (as default I/O governor)
   Other I/O governors: Noop, Deadline
   Boeffla Sound 1.6.6
   Boeffla Charge Interface
   Fading/Blinking LED
   Frandom
   
   Archi Ayarları
   - Fully optimized for Samsung Galaxy S3 (-marm -march=armv7-a -mcpu=cortex-a9 -mtune=cortex-a9 -mfpu=neon -mfloat-abi=softfp)
   - Compiled with O3 optimization level (-O3)
   - Performed interprocedural pointer analysis and interprocedural modification and reference analysis (-fipa-pta)
   - Performed loop invariant motion on trees. It also moved operands of conditions that are invariant out of the loop, so that we can use just trivial invariantness analysis in loop unswitching. The pass also includes store motion (-ftree-loop-im)
   - Created a canonical counter for number of iterations in loops for which determining number of iterations requires complicated analysis. Later optimizations then may determine the number easily (-ftree-loop-ivcanon)
   - Performed induction variable optimizations (strength reduction, induction variable merging and induction variable elimination) on trees (-fivopts)
   - Tried to reduce the number of symbolic address calculations by using shared ?anchor? symbols to address nearby objects. This transformation can help to reduce the number of GOT entries and GOT accesses on some targets (-fsection-anchors)
   - Assumed that loop indices do not overflow, and that loops with nontrivial exit condition are not infinite. This enables a wider range of loop optimizations even if the loop optimizer itself cannot prove that these assumptions are valid (-funsafe-loop-optimizations)
   - Moved branches with loop invariant conditions out of the loop (-funswitch-loops)
   - Attempted to avoid false dependencies in scheduled code by making use of registers left over after register allocation. This optimization most benefits processors with lots of registers (-frename-registers)
   - Re-ran common subexpression elimination after loop optimizations are performed (-frerun-cse-after-loop)
   - Didn't keep the frame pointer in a register for functions that don't need one. This avoids the instructions to save, set up and restore frame pointers; it also makes an extra register available in many functions (-fomit-frame-pointer)
   - Made a redundant load elimination pass performed after reload. The purpose of this pass is to clean up redundant spilling (-fgcse-after-reload)
   - Ran a store motion pass after global common subexpression elimination. This pass attempts to move stores out of loops (-fgcse-sm)
   - Eliminated redundant loads that come after stores to the same memory location, both partial and full redundancies (-fgcse-las)
   - Constructed webs as commonly used for register allocation purposes and assigned each web individual pseudo register. This allows the register allocation pass to operate on pseudos directly, but also strengthens several other optimization passes, such as CSE, loop optimizer and trivial dead code remover (-fweb)
   - Performed tail duplication to enlarge superblock size. This transformation simplifies the control flow of the function allowing other optimizations to do a better job (-ftracer)
   
   Hatalar
   1. Backlight. Sammy uses ROM handling of backlight (similar to CM), while some ROMs (i.e. Omni) stick to kernel handling. This is something I'd like to fix but it's at the bottom of my todo list, mostly because I don't care if it works or not right now. It requires kernel-handling support (i.e. Yank555 implementation) and I'd like to think how to do so in proper way.
   2. exFAT. exFAT should work just fine on most of the ROMs (Sammy + AOSP), as ArchiKernel currently has native built-in exFAT support. However, this may conflict with some ROMs which use older FUSE implementation (i.e. Omni). Newer FUSE implementation (CyanogenMod) works without problems.
   
   İndirme Linki
   Linklerin Görülmesine İzin Verilmiyor Üye ol Veya Giriş Yap
                     
                  
                  

Linkback: i9300 Galaxy S3 ArchiKernel V1.2 AOSP/Samsung/ArchiPort
  • Gösterim 1,345 
  • Samsung Galaxy S3 Custom Rom ve Geliştirme Bölümü
  • 0 Yanıtlar




Paylaş whatsappPaylaş facebookPaylaş linkedinPaylaş twitterPaylaş myspacePaylaş redditPaylaş diggPaylaş stumblePaylaş technoratiPaylaş delicious

Benzer Konular (5)


İçerik sağlayıcı paylaşım sitesi olarak hizmet veren Replikacep.com sitemizde 5651 sayılı kanunun 8. maddesine ve T.C.Knın 125. maddesine göre tüm üyelerimiz yaptıkları paylaşımlardan kendileri sorumludur.Replikacep.com hakkında yapılacak tüm hukuksal şikayetleri İletişim sayfamızdan bize bildirdikten en geç 3 (üç) iş günü içerisinde ilgili kanunlar ve yönetmelikler çerçevesinde tarafımızca incelenerek gereken işlemler yapılacak ve site yöneticilerimiz tarafından bilgi verilecektir.
Footer menü
Hakkımızda
Bize Ulaşın
Biz Kimiz
Hizmetlerimiz