I searched gitorioaus repos and found grub sources there. Actually it's confusing, because it doesn't look like bootloader for ARM device. I reviewed stage1 source and it's x86 assembler. As I know, grub is not available for ARM architecture. What others think? I guess there should be another bootloader installed for G9, like u-boot or so. It would be interesting to discover what bootloader is used in G9 and if it's under GPL to get source code.
Hi dariusa!
dariusa said:
I searched gitorioaus repos and found grub sources there. Actually it's confusing, because it doesn't look like bootloader for ARM device. I reviewed stage1 source and it's x86 assembler. As I know, grub is not available for ARM architecture. What others think? I guess there should be another bootloader installed for G9, like u-boot or so. It would be interesting to discover what bootloader is used in G9 and if it's under GPL to get source code.
Click to expand...
Click to collapse
The bootloader used on the G9 series of tablets is based on Archos proprietary source code. It has not much in common with the u-boot project.
This code is not covered by GPL and obviously there's no source code available for public.
The grub sources in the Archos Gitorious repo seem to be needed for some dependencies in the build system. At least that's what i guess...
There's no relation to any part of the bootloader we use in our G9 tablets.
Regards,
scholbert
Related
For any Developer who needs the official Viewpad 7 Kernel Source
Here it is: http://www.viewsoniceurope.com/uk/s...ystem-and-upgrade/viewpad-7-kernel-source.htm
Hopefully we can get a dev to make so we can use updated flash and get to the point of something akin to gingerbread etc for this interesting little VPad7.
Anyone close to it or is it a dead cause?
I'm adding this here as I can't get access to the main dev forum - the ITE source should be licenced under the GPL. If Viewsonic are refusing to release it, violating the GPL licence, but have released earlier source, I can only see 2 reasons:
- The ITE source contains proprietry information, it is was never intended to be linked to GPL licenced code. By releasing the code Viewsonic would be in hot legal water.
- Viewsonic haven't understood previous requests: http://forum.xda-developers.com/showthread.php?t=1360160&page=2
Either way if devs still want the ITE driver kernel source I propose we let legal team at the FSF know of this issue and let them deal with it, unless the situation has changed (that I've not read about*)? That should put a rocket up Viewsonic's behind to get the issue sorted. The FSF shouldn't have a problem issuing notice on core kernel violations as I would imagine they deal with these sort of claims regularly.
* Also checking source now (I'm not a kernel dev so I don't know exactly what I'm looking for).
Hi!
i am following this thread since 2011.
tried all the roms published but i have the same problem because there is no ite-support
i would love to try an oc-kernel!
searching all around i have found a simiular device with ite-source code published
also a 7inch display and same cpu.
if anyone is interested and able to build a kernel i will tell him where to find the source
code.
Greetings
Frank
Hello Guys,
I see a lot of threads for starting with android rom development, but can anyone give me pointers for kernel development? I would like to start kernel development and do not know where to start. I am not interested in rom development at the moment, but that is because I assume that the android rom is like a user space app over the kernel. Please correct me if I am wrong. It would be great if you guys could point me to some beginner friendly kernel development tutorials. I am looking through Linux Device Drivers (LDD) book but am having a hard time comparing that with android. I have cloned mediatek 6589 source from android repository. I am submitting partial url cos I am not allowed to submit full url yet. URL(android.googlesource.com/kernel/mediatek/+/android-5.1.0_r0.2) since I am running a mtk6589 device (Walton X1/ Gionee Dream D1) and would like to understand where to start coding kernels for android. Any help would be greatly appreciated.
Oh and I would like mediatek specific help if possible. I have gone through some of the general kernel building and overclocking tutorials. I want to do some more enhancements if possible. Since mediatek seems to be the mysterious one with bare minimum source availability, I would like to take up that challenge
Thanks.
I don't have a tutorial for you but a small checklist. You need:
* Kernel source tree
* A config for your device (e.g. arch/arm/configs/*defconfig*)
* A cross compiler toolchain to generate ARM code (you can use the precompiled one from the Android source tree)
* A way to package your kernel into a boot image for your device - usually an Android boot image contains a compiled kernel (zImage), a compressed ramdisk for the root filesystem, and probably a device tree binary (dtb). Mediatek may do things differently.
* A way to install that boot image on your device - this requires an unlocked bootloader that allows custom boot images to be installed and started. Most devices use the fastboot tool for this.
Your first step should be to build a working kernel from unmodified sources. When you got that working, you can think about starting actual coding.
Thanks for the Pointer Mate
_that said:
I don't have a tutorial for you but a small checklist. You need:
* Kernel source tree
* A config for your device (e.g. arch/arm/configs/*defconfig*)
* A cross compiler toolchain to generate ARM code (you can use the precompiled one from the Android source tree)
* A way to package your kernel into a boot image for your device - usually an Android boot image contains a compiled kernel (zImage), a compressed ramdisk for the root filesystem, and probably a device tree binary (dtb). Mediatek may do things differently.
* A way to install that boot image on your device - this requires an unlocked bootloader that allows custom boot images to be installed and started. Most devices use the fastboot tool for this.
Your first step should be to build a working kernel from unmodified sources. When you got that working, you can think about starting actual coding.
Click to expand...
Click to collapse
Thanks man. Really appreciate the pointers. I do have some of the checklists done. Like
* Kernel source tree
** A cross compiler toolchain to generate ARM code (using the precompiled one)
* A way to install that boot image on your device
Now the problem is, my device still does not have its source code available. I got the general source tree from google which is not my device's so I dont have the defconfig. Is there a way to rip it out from a compiled kernel? Like using some sort of a decompiler? Also I will look around for zimage packaging tools. Thanks mate. Mediatek is apparently one hell of a problem child XD
syko_kickass said:
Now the problem is, my device still does not have its source code available. I got the general source tree from google which is not my device's so I dont have the defconfig. Is there a way to rip it out from a compiled kernel? Like using some sort of a decompiler? Also I will look around for zimage packaging tools.
Click to expand...
Click to collapse
If you're lucky, your existing kernel exposes its config in the file /proc/config.gz. If not, I don't know how to get a matching config - best is to avoid buying anything from GPL violators.
I have a cheap Polaroid tablet P902/A900 made by Southern Telecom with a rockchip processor.
I want to compile a custom recovery for it but the kernel source is not available on their website and they are ignoring my requests via email and their support forms.
Is there anything that I can do to get it?
I thought that due to the GPL, the kernel source had to be available for all android devices.
Is that not the case?
opticyclic said:
I have a cheap Polaroid tablet P902/A900 made by Southern Telecom with a rockchip processor.
I want to compile a custom recovery for it but the kernel source is not available on their website and they are ignoring my requests via email and their support forms.
Is there anything that I can do to get it?
I thought that due to the GPL, the kernel source had to be available for all android devices.
Is that not the case?
Click to expand...
Click to collapse
no it's not available to all devices
messi2050 said:
no it's not available to all devices
Click to expand...
Click to collapse
Are you just stating the fact that it isn't available for all devices or are you saying that the android kernel is not GPL and that kernel source doesn't have to made available for all devices?
opticyclic said:
Are you just stating the fact that it isn't available for all devices or are you saying that the android kernel is not GPL and that kernel source doesn't have to made available for all devices?
Click to expand...
Click to collapse
No I'm just saying that not all the vendors release their devices sources
OK. Thanks.
However, they are supposed to as part of the GPL though right?
I found this snippet on the CyanogenMod wiki saying as much http://wiki.cyanogenmod.org/w/Doc:_porting_intro#Collect_any_available_existing_source_code
It makes the GPL seem a bit impotent if manufacturers can flaunt the license terms as they please.
opticyclic said:
I have a cheap Polaroid tablet P902/A900 made by Southern Telecom with a rockchip processor.
I want to compile a custom recovery for it but the kernel source is not available on their website and they are ignoring my requests via email and their support forms.
Is there anything that I can do to get it?
I thought that due to the GPL, the kernel source had to be available for all android devices.
Is that not the case?
Click to expand...
Click to collapse
not all oem will release their source code in fact,some well known device manufacturer will release their source code and some unknown device or unpopular device (sorry but no sorry) will not because it is costly and not free,it depends on many factor, so the source code you requested from the manufacturer may or may not got released through their website.
Hello guys.
This question is specially for devs or advanced users with development skills.
My question is related to the kernel source of one of my devices, Huawei Mediapad T1 10 (codename: hwt1a21l). I got the kernel source from the oficial Huawei website and uploaded it to a github repo. My device, which has a msm8916 chiset, doesn't have any development (roms, recoveries, device tree, etc) and his rom, EMUI 3.0, is based on Kit Kat 4.4.2.
I have been trying to bring development for this tablet many months ago because the stock rom is too deprecated for the hardware that has, with the msm8916 there is a huge potential to bring it a lot of development.
Well, i'm going to summarize my problems when trying to bring development for the device:
To get started development, for example a LineageOS build i needed a solid base to start with: device tree, propietary blobs and kernel source, so i got all of them. I ported the device tree from another one very similar to mine (with the same chipset), extracted the propietary blobs with the build tools from the source and got the kernel source from the Huawei website. So everything seemed to be good, but when i start the build process with my Linux machine (repo sync > source build/envsetup.sh > breakfast hwt1a21l > brunch hwt1a21l) i always receive thousands of build error by the kernel source, and i have been fixing (or at least avoid) a lot of them but it never ends, so i don't know if it's worth to keep trying to "fix" them or if i'm wasting my time.
So, what i have been trying to do: i have been trying to build a LineageOS 14.1 and TWRP recovery with my device tree This: Mustang-ssc/android_device_huawei_msm8916-common ported from this one from @dianlujitao : dianlujitao/android_device_huawei_msm8916-common and the specific kernel source for my device downloaded from the Huawei website Mustang-ssc/android_kernel_huawei_hwt1a21l. Here ends the summary.
So after a lot of hours, days and nights over the last months trying to make progress with this and not getting any help from the few devs i asked after seeing my lack of progress i decided to publicly ask for help.
The questions:
1. I have the official kernel source (Mustang-ssc/android_kernel_huawei_hwt1a21l) which i didn't have success to compile it, and then i saw the kernel source from a device almost identical to mine (same chipset, brand, ram, ...) (dianlujitao/android_kernel_huawei_msm8916). Can i use that kernel source as a base for my device after porting the specific configurations of my official kernel source (defconfig, drivers, libraries)? That one is much more updated and probably optimized than mine, but i don't know if it's possible to adapt a kernel source from other device using your kernel source.
2. This may be a dumb question: my device has Kit Kat 4.4.2. Is there any link between the kernel source and the android version the device has? I mean, i don't know if i should do something to adapt my kernel source for newer android versions (Marshmallow, Nougat) of if it's ok to just build with it without any change.
If you read it all, congratulations, you're awesome
Still waiting for a reply
Where can I found the source code for build android for Alcatel pop c7 ?
I wrote a whole piece on how you could contact them, but they actualy shared sources for alott of their phone's and such already.
But that doesnt make it a ready 1-2-3 step compile android for yourself Ow no, Alcatel like many companies only comply by the licenses to share any source they used or modifications they made if required by lisences. If they have a NDA with Mediatek (wich they do) they are probably not required to include proprietary software, tools or sources they got from mediatek.
Think mediatek chipset specific header files, drivers, firmware (only binairy blobs might be shared). maybe they share enough for you to compile a working kernel and filesystem, but no signing keys, maybe the resulting files will run on a rooted, Custom firmware phone but No updates, some hardware not working, maybe the phone funstion doesnt work (due to missing specific code to use the mobile chipset).
Quick google, Alcatel shared it on sourceforge: https://sourceforge.net/projects/alcatel/files/ search for (ctr+f)
Code:
OT_7041_20141204.tar.xz
A quick look inside reveals alott of the expected sources, generic hardware support and specific drivers (in blob form it seems). A readme with instructions seem to be included, but very basic,
So, here you go. The "sourcecode". all 162MB of it. or go search on Baidu, maybe an ex dev leaked internl documents and firmware sources :fingers-crossed: maybe this is just what you needed, enjoy