Database Develop

dell kernel source ?

i am trying to compile kernel src from dell with android ndk. i got this error
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mabi=apcs-gnu"
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
where can i find nvidia src from how_to_build.txt ?
thanks

mashi said:
i am trying to compile kernel src from dell with android ndk. i got this error
SYMLINK include/asm -> include/asm-arm
CC kernel/bounds.s
cc1: error: unrecognized command line option "-mlittle-endian"
cc1: error: unrecognized command line option "-mapcs"
cc1: error: unrecognized command line option "-mno-sched-prolog"
cc1: error: unrecognized command line option "-mabi=apcs-gnu"
kernel/bounds.c:1: error: bad value (armv5t) for -march= switch
kernel/bounds.c:1: error: bad value (armv5t) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
where can i find nvidia src from how_to_build.txt ?
thanks
Click to expand...
Click to collapse
I told you the other day how to fix that stuff... You're not specifying the cross compiler to use.
export PATH=$PATH:/media3/android/ds7/dev/arm-2010q1/bin
export CROSS_COMPILE=arm-none-linux-gnueabi-
export ARCH=arm
Using CodeSorcery. If you're using something else, substitute, and of course update the path.
As for the nvidia source.. I never did find 2.6.32.9 from nvidia, but I did find this..
http://developer.nvidia.com/tegra/forum/build-android-source-tegra-250
From which I was able to grab it. Then I ran into this:
http://developer.nvidia.com/tegra/forum/linux-kernel-compilation-error-when-building-confignfsfsm
In the end, either source of the kernel I used, one gave me that the symbol map didn't match (using Dell source 3.36) and the other I kept getting the outer_cache symbol missing (from the nvidia source).
I suspect that it's just a matter of setting up the kernel correctly. I'm using /proc/config.gz but I googled around a bit and some folks here on XDA building a kernel on a phone were saying they had to add some extra parameters given to them by Samsung before being able to successfully build a module that would work for their phone.
Hopefully one of us figures it out... You want CIFS, I want TUN.

echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin:/home/alan/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin
echo $CROSS_COMPILER
/home/alan/android-ndk-r5c/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
echo $ARCH
arm
I have set all those path before compile the kernel
khaytsus said:
I told you the other day how to fix that stuff... You're not specifying the cross compiler to use.
export PATH=$PATH:/media3/android/ds7/dev/arm-2010q1/bin
export CROSS_COMPILE=arm-none-linux-gnueabi-
export ARCH=arm
Using CodeSorcery. If you're using something else, substitute, and of course update the path.
As for the nvidia source.. I never did find 2.6.32.9 from nvidia, but I did find this..
http://developer.nvidia.com/tegra/forum/build-android-source-tegra-250
From which I was able to grab it. Then I ran into this:
http://developer.nvidia.com/tegra/forum/linux-kernel-compilation-error-when-building-confignfsfsm
In the end, either source of the kernel I used, one gave me that the symbol map didn't match (using Dell source 3.36) and the other I kept getting the outer_cache symbol missing (from the nvidia source).
I suspect that it's just a matter of setting up the kernel correctly. I'm using /proc/config.gz but I googled around a bit and some folks here on XDA building a kernel on a phone were saying they had to add some extra parameters given to them by Samsung before being able to successfully build a module that would work for their phone.
Hopefully one of us figures it out... You want CIFS, I want TUN.
Click to expand...
Click to collapse

I'll be following this thread as I'm trying to figure this out, too (I'm very much a Linux n00b, though, so the progress is incredibly slow). I think the kernel compilation is the main thing holding us back from getting some custom ROMs on here; once the parameters of the build environment are found, we'll probably have an easier time of it (and, good as DJ_Steve is, it would be nice to have a few more devs working this device).
Does this link help at all?
http://opensource.dell.com/releases/streak7/3.36/HOW-TO-BUILD.txt

Z4nd4r said:
I'll be following this thread as I'm trying to figure this out, too (I'm very much a Linux n00b, though, so the progress is incredibly slow). I think the kernel compilation is the main thing holding us back from getting some custom ROMs on here; once the parameters of the build environment are found, we'll probably have an easier time of it (and, good as DJ_Steve is, it would be nice to have a few more devs working this device).
Does this link help at all?
http://opensource.dell.com/releases/streak7/3.36/HOW-TO-BUILD.txt
Click to expand...
Click to collapse
Not really, at least not me.. First off finding nvidia Froyo source was a PITA and I only got it from a clone of the old repo so no tellling there.. Plus the other steps seem to mostly be nonsense, as files don't match up, etc..
Otherwise, I can readily compile the Dell code but the output won't load.. Symbol map does not match; ie: config is different. Maybe even compiler differences.. Dunno.

Im sorry for my noobness, but what would this code actually do for us? Would we then have the ability to compile our own kernels and overclock and whatnot?

ssmr2t said:
Im sorry for my noobness, but what would this code actually do for us? Would we then have the ability to compile our own kernels and overclock and whatnot?
Click to expand...
Click to collapse
Maybe, but I just want tun.ko for now. Still no luck today, switched to Android NDK but still symbol issues.
Sent from my Dell Streak 7 using Tapatalk

If u can catch it compiler version is output through dmesg during bootup I don't have me streak handy or I would check. Compiler version may very well play a roll in modules loading though I have experienced it on x86 anyway

Brandas said:
If u can catch it compiler version is output through dmesg during bootup I don't have me streak handy or I would check. Compiler version may very well play a roll in modules loading though I have experienced it on x86 anyway
Click to expand...
Click to collapse
Good idea, but it doesn't seem to have much info..
<5>[ 0.000000] Linux version 2.6.32.9 ([email protected]) (gcc version 4.4.0 (GCC) ) #8 SMP PREEMPT Mon Mar 28 14:04:54 CST 2011

Thread Resurrection in progress.
I'm going to be adding FTDI VCP support. Figured I'd post here to see what progress others have made... was a little surprised to only find 2 dev pages for this tablet.

Yeah, I've been working on a 2.6.35 kernel myself slowly, but I totally screwed it up and need to start over.

Maybe who try developing kernel should search help in other tegra2 device forums
Sent from my LG-P500 using Tapatalk

nikoltu said:
Maybe who try developing kernel should search help in other tegra2 device forums
Click to expand...
Click to collapse
Any particular forum you have in mind? I did take a look at the somewhat updated Dell Opensource page:
http://opensource.dell.com/releases/streak7/5.06/
But it is definitely aimed at HC, and I don't think it would do much for an ICS build. On the other hand, at least it gives what "appears" to be the source and binaries for the devices (though I'm a little more inclined to use what I was able to pull off the device with ADB).
FWIW...
---------- Post added at 11:52 AM ---------- Previous post was at 11:33 AM ----------
One other link that appears to be of interest:
http://developer.nvidia.com/tegra-resources
Note the releases as of 12/19 of updated Tegra kits

The info from opensource.dell.com is missing a lot of information.

[Q] Kernel compile error

Hey there all
I'm trying to compile a kernel for the GT-I9070P from the default Sammy source (opensource.samsung.com) and I've encountered an error and I hope you guys can help me with this:
Code:
drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.c: In function 'cm_DSP_AcknowledgeDspIrq':
drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.c:315:5: error: variable 'dummy' set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
make[3]: *** [drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.o] Error 1
make[2]: *** [drivers/staging/nmf-cm] Error 2
make[1]: *** [drivers/staging] Error 2
make[1]: *** Waiting for unfinished jobs....
I wonder if any of you guys have encountered these errors.....

Hi.
Dont use GCC 4.5+ to build kernel.
If you still wanna use GCC 4.5+, here is a method:
In your /drivers/staging/nmf-cm/makefile, just delete "Werror".
And build it again.
Recommend using Linaro GCC 4.4.5 or GCC 4.4.3 .
EDIT:
Although you can have a booting kernel, but the phone will reboot immediately when you dial out.
I replacd dsp.c from other source code, and it built with no errors.
The phone still will reboot when dial out.

Hmm....so that means the phone will reboot upon attempting to call someone ?
I give up writing anymore signatures.

CallMeVentus said:
Hmm....so that means the phone will reboot upon attempting to call someone ?
I give up writing anymore signatures.
Click to expand...
Click to collapse
Yep, when some calls come it will reboot, too.
It has no reboot issue with gcc 4.4
BTW,sorry, just now i replied a wrong thread.

cocafe said:
Yep, when some calls come it will reboot, too.
It has no reboot issue with gcc 4.4
BTW,sorry, just now i replied a wrong thread.
Click to expand...
Click to collapse
Nah it's fine , I believe you just saved my ass
I give up writing anymore signatures.

Thread moved to General section.

[Q] Cannot wrap my head around these kernel build errors

Hello all, I was trying to cook up this AOKP based rom last night, and I let it build overnight as I usually do.
This morning, I woke up to:
Code:
make[6]: *** [drivers/net/wireless/bcmdhd/dhd_linux.o] Error 1
make[5]: *** [drivers/net/wireless/bcmdhd] Error 2
make[4]: *** [drivers/net/wireless] Error 2
make[3]: *** [drivers/net] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/nathan/AICP/kernel/htc/m7'
make: *** [TARGET_KERNEL_BINARIES] Error 2
I was going to use a prebuilt, but when I go to my m7spr directory (straight from AOKP source) I didn't see a kernel folder.
I know that I need to edit TARGET_KERNEL_BINARIES in BoardConfig.mk for m7-common, but I edited it to "aokp_m7_defconfig" and nothing changed. Please help and thank you in advance!!

That really doesn't show what the error is, just that there is an error.
Sent from my HTCONE

thicklizard said:
That really doesn't show what the error is, just that there is an error.
Sent from my HTCONE
Click to expand...
Click to collapse
I was hoping that someone might recognize this or something but I run into almost every time.
Installed a package that someone said would fix the problem, and I'm anxious to see if it works, but it will have to be until tonight.
Also, I discovered that java 7 doesn't play well with kitkat. For some reason, you can use 7 to build jb, but if you use it with kitkat you will have issues. I installed 7 to use netflix on ubuntu, but I reverted to 6. The combination of those two things will hopefully fix it, if not I'll be back
Thank you for your help.

nathantaylor said:
I was hoping that someone might recognize this or something but I run into almost every time.
Installed a package that someone said would fix the problem, and I'm anxious to see if it works, but it will have to be until tonight.
Also, I discovered that java 7 doesn't play well with kitkat. For some reason, you can use 7 to build jb, but if you use it with kitkat you will have issues. I installed 7 to use netflix on ubuntu, but I reverted to 6. The combination of those two things will hopefully fix it, if not I'll be back
Thank you for your help.
Click to expand...
Click to collapse
I would have to see the exact error in that .c file
Sent from my HTCONE

thicklizard said:
I would have to see the exact error in that .c file
Sent from my HTCONE
Click to expand...
Click to collapse
Yeah, I'm long past that terminal window now but if it ever comes up again I'll try and DM you or something.... Thank you
Sent from my Nexus 7 using Tapatalk 4

You can and will have many unidentifiable errors based on Java 7. In my experience, even having 6 installed won't help forever because somehow 7 will inadvertently be tripped; no idea why. This is what I did:
http://forum.xda-developers.com/showpost.php?p=47782603&postcount=4978
Hope it helps....

[Q] Help building CM for Nook HD+

I've been running CM on my HD+ for the last few months and it's been great. I'm working on making some modifications to the VM and to the kernel and it requires building CM from source. I've already done this with several other devices and have had only minor problems. I'm following the instructions and it can't build. I get the following error:
Code:
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3.1
CM_VERSION=10.2-20140120-UNOFFICIAL-ovation
TARGET_PRODUCT=cm_ovation
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.7.10-1.16-desktop-x86_64-with-SuSE-12.3-x86_64
HOST_BUILD_TYPE=release
BUILD_ID=JLS36I
OUT_DIR=/home/david/Android/system/out
============================================
make: *** /.config: Is a directory. Stop.
I've searched and haven't found a solution but It seems like I'm missing a manifest or something. I'm wondering if this is missing from 10.2 and I should just try building 11 or if there's a way I can build from source.
Thanks to anyone who can help!

No experience building CM but it looks like maybe /.config instead of ./config got invoked?
Sent from HD+ MAG2GA CM 11 from SD

Did you follow this guide? -> http://wiki.cyanogenmod.org/w/Build_for_ovation (repo init for cm11 instead if cm11 is desired)
Its probably just an error that you made. I don't remember seeing it before.
Edit it doesn't like /.config. That much is obvious. So try to rename or move it or fix your problem to avoid it. (if its ~/.config be careful as that is an important dir.)
There is a .config in /out during building process which is the kernel defconfig file. There is also ~/.config. And that's all I know about that. Look around for .config or google your error with "/.config;" removed and see how the "make: *** is a directory. stop" plain version helps you.

I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.

ddpruitt said:
I followed the guide in the wiki but it's a no go. I removed and resynced just in case something didn't pull correctly (wouldn't be the first time). I'm grepping the makefiles for .config to try and narrow down the problem but it doesn't seem to be helping. I've compared the structures of the Galaxy Nexus and the Nook build trees and I don't see any huge differences.
<edit>
Found a bunch of config files but no .config, now I'm even more confused.
Click to expand...
Click to collapse
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Some other thoughts based on testing:
You get the correct manifest, etc. with the git and repo sync so again its not with what your getting. That all will build it without that weird error.
If there's no .config file in android/system/out/target/product/ovation/obj/KERNEL_OBJ/ then its because it didn't do enough to put one there yet. That shouldn't be the issue as it will rename a .config dir and continue or if it can't then have a different error.
Did you try make clean or make clobber and try building again?

sandsofmyst said:
It shouldn't be in what you received with the guide as your getting the device repo, but how you did it or something that is not configured correctly on your os.
Its a bit confusing but the error says what it wants and that's the key.
Edit: Tried to get my build to do the same but no go. Out of ideas for you. Sorry
Click to expand...
Click to collapse
I had someone else try it on an Ubuntu machine and it has the same issue. I'll try to get the verygreen repos instead of the official CM ones see if that helps

Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.

sandsofmyst said:
Duplicated! ...
You have a .config directory in /
Exactly as the error says as I get the same error only by creating one there. Or I should say the exact same error line and no building.
Click to expand...
Click to collapse
You're an absolute genius. For some reason I did have a /.config directory, I never even though of looking in the root directories. Must be some strange KDE issue. I deleted it and build kicked off and it's rolling fine now.

Having an issue building cyanogenmod 13.0

Hey guys,
I'm having an issue when building cyanogenmod 13.0. It gets to about 20 min into the build, then fails with this error:
Code:
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:57: HSIC cannot be resolved to a type
make: *** [/home/edwin/phonelab/cm-shamu/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41
if anyone can point me in the right direction to get this straightened out I'd be appreciative.

saintsantos said:
/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type.
Click to expand...
Click to collapse
I am building CM-13.0 for LG G4 H811 and found the same problem. It's due to
Change 153678 - cmhw: Add PictureAdjustment stubs
which was just merged this morning. This is the sort of glaring bug that will be found and corrected quickly. Sometimes I wonder whether some folks actually build their code before merging it.
Edit to add:
14:00 EDT - I checked the change comments and the senior devs are aware of the problem and are working on it.

It was reverted about 20 minutes ago. You can either repo sync again, or cd to frameworks_opt_hardware and git revert a8ef044be1eb70c0f8a17f0c40d4c5c08bf71593
http://review.cyanogenmod.org/#/c/153678/

saintsantos said:
Hey guys,
I'm having an issue when building cyanogenmod 13.0. It gets to about 20 min into the build, then fails with this error:
Code:
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:57: HSIC cannot be resolved to a type
make: *** [/home/edwin/phonelab/cm-shamu/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41
if anyone can point me in the right direction to get this straightened out I'd be appreciative.
Click to expand...
Click to collapse
Same issue here when building for jem (the Amazon Kindle Fire HD 8.9"). I'm going to run repo sync and rebuild as suggested in post #3.

Neo said:
It was reverted about 20 minutes ago. You can either repo sync again, or cd to frameworks_opt_hardware and git revert a8ef044be1eb70c0f8a17f0c40d4c5c08bf71593
http://review.cyanogenmod.org/#/c/153678/
Click to expand...
Click to collapse
Thanks. I reverted the commit in my repo anyway, but I'm just glad it was caught and handled.