Database Users

Android source officially released!

Ok so google has now officially released the android source code and SDK. So now there are endless possibilities to what can be done with it, it can be ported to any device.
I'll leave the devs to think about that but till then heres the link:
http://source.android.com/ Info about the source
http://code.google.com/android/ Download SDK from here.
xmOD

I5800 Drivers

Ok I admit that this might be a silly question, but here it goes:
In the froyo open source kernel from samsung open source release center, there is a file called 'drivers'. Are these the drivers from the phone's hardware? If that's the case then it is possible to compile the 2.3 kernel based on those drivers (provided that you download the 2.3 kernel from google).

Anyone have used this RK3066 development Board?

I just searched ebay for RK3066 Development Board, and found one there, I have played the Beagle board.
this one seem good for play with RK3066 firmware and debug rom.

wy6688 said:
I just searched ebay for RK3066 Development Board, and found one there, I have played the Beagle board.
this one seem good for play with RK3066 firmware and debug rom.
Click to expand...
Click to collapse
Not used that one, but I'd caution you away from the RK3066 in general, as I have used a device with RK3066 chipset...
Rockchip don't respect or follow the GPL and give sources with binaries included. This means you cannot compile entirely from source, and can be problematic. Some core drivers like the clock driver are blobbed.
There may be better development boards out there, the ODroid X2 is one I've heard good things about.

I have checked the Latest Linux Kernel source from Kernel.org, all their source code included, using new ARM DTS system (device tree source), so you can compile all your kernel directly from mainstream kernel, except some board level chip driver, which you need to customize from Driver fold, /linux/arch/arm/boot/dts/rk3066a.dtsi, rk3066a-clocks.dtsi

wy6688 said:
I have checked the Latest Linux Kernel source from Kernel.org, all their source code included, using new ARM DTS system (device tree source), so you can compile all your kernel directly from mainstream kernel, except some board level chip driver, which you need to customize from Driver fold, /linux/arch/arm/boot/dts/rk3066a.dtsi, rk3066a-clocks.dtsi
Click to expand...
Click to collapse
Have you got NAND drivers for the rk3066 nand? clock drivers, ddr drivers?
(see files with a .uu extension, it's a uuencoded .o binary)
https://github.com/AndrewDB/rk3066-kernel/tree/master/arch/arm/mach-rk30 (ddr.uu, ddr_freq.uu, clock_data.uu)
https://github.com/AndrewDB/rk3066-kernel/tree/master/drivers/video (fb.uu)
I believe there's also some missing drivers for the nand (https://github.com/AndrewDB/rk3066-kernel/tree/master/drivers/mtd/rknand)

I just got the development broad from ebay and checked the source code, it do missing these source file and although you can build the kernel without issue for 3.0.8.
I believe the latest 3.10.x kernel from kernel org, which included the RK3066 DTS files, can be used to build the generic kernel that can run on RK3066 board and should have no other source code needed.
I'm trying to build this kernel based on 3.10.x, anyone know detail steps that build the generic kernel based on RK3066 DTS?
Thank advance.

Cross Compiler Toolchains [GNU GCC 5.3] [Cortex Optimized]

Hello dear developers, I'm releasing here my self build custom toolchains for various devices!
First of all I want to say thank you to @Christopher83 who made the basics and I adapted it to work on generic GNU (instead of linaro) cross compilers. I got the same flags to compile the for the different cortex cpu's.
If you have any requests or questions, please just ask. I'll try to answer them.
Please hit thanks if you like this work!
Also, if you want to see the exact sample files used, you can visit my github page at: crosstool-ng
Supported are:
- Generic CPU
- Cortex A9
- Cortex A8
- Cortex A7
- Cortex A15
The toolchains with arm-cortex_a15-linux-gnueabihf prefix are optimized for Cortex-A15 cpu with Neon-VFPv4 technology support.
The toolchains with arm-cortex_a9-linux-gnueabihf prefix are optimized for Cortex-A9 cpu with Neon-VFPv3 technology support.
The toolchains with arm-cortex_a8-linux-gnueabi prefix are optimized for Cortex-A8 cpu with Neon-VFPv3 technology support.
The toolchains with arm-cortex_a7-linux-gnueabihf prefix are optimized for Cortex-A7 cpu with Neon-VFPv4 technology support.
The toolchains with arm-cortex-linux-gnueabi, arm-linux-gnueabi or arm-unknown-linux-gnueabi prefix are built for generic Cortex-A cpu and configured with similar settings to those of the latest GNU toolchains, the tools and libraries inside them are built with Thumb-2 (for architecture) and VFPv3-D16 (for fpu) instruction sets support.
Config options that are used:
Christopher83 said:
Config options used for the toolchains optimized for Cortex-A15 cpu with Neon-VFPv4 technology support
Code:
CT_ARCH_ARCH=""
CT_ARCH_CPU="cortex-a15"
CT_ARCH_TUNE="cortex-a15"
CT_ARCH_FPU="neon-vfpv4"
CT_ARCH_FLOAT_HW=y
CT_ARCH_FLOAT="hard"
CT_ARCH_SUPPORT_SOFTFP=y
CT_ARCH_ARM_MODE="arm"
CT_ARCH_ARM_MODE_ARM=y
Config options used for the toolchains optimized for Cortex-A9 cpu with Neon-VFPv3 technology support
Code:
CT_ARCH_ARCH="armv7-a"
CT_ARCH_CPU="cortex-a9"
CT_ARCH_TUNE="cortex-a9"
CT_ARCH_FPU="neon"
CT_ARCH_FLOAT_HW=y
CT_ARCH_FLOAT="hard"
CT_ARCH_SUPPORT_SOFTFP=y
CT_ARCH_ARM_MODE="arm"
CT_ARCH_ARM_MODE_ARM=y
Config options used for the toolchains optimized for Cortex-A8 cpu with Neon-VFP3 technology support
Code:
CT_ARCH_ARCH="armv7-a"
CT_ARCH_CPU="cortex-a8"
CT_ARCH_TUNE="cortex-a8"
CT_ARCH_FPU="neon"
CT_ARCH_FLOAT_SOFTFP=y
CT_ARCH_FLOAT="softfp"
CT_ARCH_ARM_MODE="arm"
CT_ARCH_ARM_MODE_ARM=y
Config options used for the toolchains optimized for Cortex-A7 cpu with Neon-VFPv4 technology support
Code:
CT_ARCH_ARCH=""
CT_ARCH_CPU="cortex-a7"
CT_ARCH_TUNE="cortex-a7"
CT_ARCH_FPU="neon-vfpv4"
CT_ARCH_FLOAT_HW=y
CT_ARCH_FLOAT="hard"
CT_ARCH_SUPPORT_SOFTFP=y
CT_ARCH_ARM_MODE="arm"
CT_ARCH_ARM_MODE_ARM=y
Config options used for the generic toolchains for Cortex-A cpu (similar to latest Linaro toolchain builds)
Code:
CT_ARCH_ARCH="armv7-a"
CT_ARCH_CPU=""
CT_ARCH_TUNE="cortex-a9"
CT_ARCH_FPU="vfpv3-d16"
CT_ARCH_FLOAT_SOFTFP=y
CT_ARCH_FLOAT="softfp"
CT_ARCH_ARM_MODE="thumb"
CT_ARCH_ARM_MODE_THUMB=y
Click to expand...
Click to collapse
Download:
GNU GCC Cross Compiler Toolchain: GCC 5.3 folder
Credits to:
@Cristopher83
All people who contribute to Crosstool-NG
XDA:DevDB Information
Cross Compiler Toolchain, Tool/Utility for all devices (see above for details)
Contributors
Tkkg1994
Source Code: https://github.com/S5-APQ8084/crosstool-ng
Version Information
Status: Stable
Current Stable Version: 5.3
Stable Release Date: 2016-03-07
Created 2016-03-07
Last Updated 2016-03-07

Changelog
GNU GCC 5.3 Changelog/Features:
- Linux Target Version: 3.10.98
- BINUTILS V2.26
- LIBC V2.23
- GCC 5.3
- GDB V7.11
- GMP V6.1.0
- ISL V0.14
- EXPAT V2.1.0
- NCURSES V6.0

Reserved

one more

last one

Thank you! Will test in the next days! ?

Holy thanks man! I'm going to try out your cortex a15 hard float literally right now!
One tiny question.
Should I be using the above config options (for the specific toolchain, of course) in my already customized .config, or adjusting my Makefiles? Or are those just referenced examples to the toolchain's pre-configured values?

robcore said:
Holy thanks man! I'm going to try out your cortex a15 hard float literally right now!
One tiny question.
Should I be using the above config options (for the specific toolchain, of course) in my already customized .config, or adjusting my Makefiles? Or are those just referenced examples to the toolchain's pre-configured values?
Click to expand...
Click to collapse
These are just references of how the toolchain was build. So nothing you have to add to your source code
Sent with my SM-G930F powered by SuperMan

Tkkg1994 said:
These are just references of how the toolchain was build. So nothing you have to add to your source code
Sent with my SM-G930F powered by SuperMan
Click to expand...
Click to collapse
Sweet! Thanks again man : ) you are a kick-arse programmer, and I've learned so much from your work, its much appreciated!
Ps if you're ever working on jflte stuff in the future, I fixed faux sound 3 for speaker control found here:
https://gist.github.com/robcore/1b984e4a16faecd3c2e9058e7b34d7b6

robcore said:
Sweet! Thanks again man : ) you are a kick-arse programmer, and I've learned so much from your work, its much appreciated!
Ps if you're ever working on jflte stuff in the future, I fixed faux sound 3 for speaker control found here:
https://gist.github.com/robcore/1b984e4a16faecd3c2e9058e7b34d7b6
Click to expand...
Click to collapse
I got an s7 now so I don't need any faux sound at the moment
Sent with my SM-G930F powered by SuperMan

Sweet! Toolchain is working perfectly by the way

robcore said:
Sweet! Toolchain is working perfectly by the way
Click to expand...
Click to collapse
I know, I always use it to build my kernels
Sent with my SM-G930F powered by SuperMan

nvidia shield free software foundation certification

I know nvidia released lots of open source code and now with the possessor hack can we get a free software foundation certified shield with a open boot-loader, drivers and linux distro without binary blobs ?
sorry if i sound noobish

linux-user said:
I know nvidia released lots of open source code and now with the possessor hack can we get a free software foundation certified shield with a open boot-loader, drivers and linux distro without binary blobs ?
sorry if i sound noobish
Click to expand...
Click to collapse
I think you should only download the software available on the CHplay store

The processor hack has nothing to do with that stuff. Nvidia just won't release the source code for the drivers.