Hello,
I have found the source code for my light sensor (AS3676) from the chip manufacturer. I once compared the source code of the chip manufacturer with the source code of the Sony - partially differences. Now, my question - can the source code from chip manufacturer on my Arc kernel can be compiled?(think is a stupid question...)
Or give it some arc Kernels (for ics) that always do?
The leds-as3676.c file - it take sometime a very long time to open it
Code:
https://android.googlesource.com/kernel/msm.git/+/eaf36994a3992b8f918c18e4f7411e8b2320a35f/drivers/leds/leds-as3676.c
Related
I know Motorola opens Defy's kernel source code on sourceforget.
But I can't find any README or INSTALL documents on source code.
How to build Defy's kernel from source??
I doubt they did, and I doubt it is possible to use this kernel.
Any link?
Believe this is what he's talking about:
http://sourceforge.net/projects/moto-defy.motorola/files/DEFY TMO/3.4.2-107-JDN-9/
Hello,
I am new to this forum (even if I have been reading it for a few months already/ I am myself a software developer) and I have some questions concerning the port of ICS to the Desire HD.
I am mainly concerned about our options to implement GPU HW acceleration. As far as I know, the Adreno 205 driver source code is not public.
- Do we need to wait a new release from Qualcomm ?
- Is there a possibility to do some reverse-engineering and possibly hack the current driver to make it work with ICS ?
- Can we use the current driver and 'modify/hack' ICS source code ?
- I suppose we can wait for an official driver for a different phone using the same GPU and 'hack' it to make it work on our device ?
Thank you for any help or suggestions.
The status is, that freexperia cm9 sneak preview hs hw acceleration enabled and the xperia has the same gpu as the dhd. ( http://forum.xda-developers.com/showpost.php?p=19777780&postcount=2013 )
But the problem is that their git tree has not been updated with the hw acceleration patches and therefor contains nothing of use to the dhd port. ( https://github.com/freexperia and http://forum.xda-developers.com/showpost.php?p=19777780&postcount=2013 ) There are currently several Posts in the freexperia thread urging them to update their git.
Also there is the following status on how and what to do about drivers: http://rootzwiki.com/topic/10447-adreno200-source-code-userspace-driver/#entry54129
Thank you very much. A lot of devices use the MSM8255 snapdragon system so I guess as soon as one of them has HW acceleration working, it should be possible to implement it on the DHD too.
I cannot wait to know more about those patches for the xperia ARC
The camera is better in the Sony stock ROM compared with for example CM. I have understood that this is due to the driver being closed source, owned by Sony.
How possible is it that the open source camera will be as good as the proprietary one?
Has Sony ever before released the sources for their other camera drivers, or have they released the driver as a binary blob usable in other ROMs?
I am asking just out of curiosity.
How to port custom kernels from P8000 to another device running the MT6753?
You need to check which hardware (LCD, Touchpanel, Camera, ...) is built in and find driver sources. Luckily the P8000 kernel source is rather big and contains a lot of unused drivers so there might be a fair chance to port it to devices. There are also other sources around in the Internet so start searching
BlueFlame4 said:
You need to check which hardware (LCD, Touchpanel, Camera, ...) is built in and find driver sources. Luckily the P8000 kernel source is rather big and contains a lot of unused drivers so there might be a fair chance to port it to devices. There are also other sources around in the Internet so start searching
Click to expand...
Click to collapse
Is there any step by step guide for kernel porting?
Hello,
I have some general questions about the differences and particularities of Android ROM programming:
1. AOSP is the device-independent source of all ROMs. Where exactly is the dividing line between the general device-independent code and the device-specific code, or, in other words: Which diretories are relevant when you want to fix hardware problems or port a ROM to another device?
2. How deep do you have to dig into the system in order to port a ROM? On the lowest level you have ARM assembly, on the intermediate level C/C++ and on the highest Java. Do you need much knowledge about Linux
kernel programming in order to port a ROM and make all hardware work properly?
3. Is it possible to trace a hardware-specific function call in the stock ROM and then paste the relevant code from the stock ROM into the custom ROM?
I'm asking because I would like to port a ROM, but I need some background information in order to assess my skills. Thanks for any help.
There is much hardware specific code in the modified Linux kernel. That's why lineageOS bringup has to start with release of stock ROM kernel source code.