dell kernel source ?

[mashi]

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

 

[khaytsus]

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

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.

 

[mashi]

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

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.

 

[Z4nd4r]

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

 

[khaytsus]

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

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.

 

[ssmr2t]

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?

 

[khaytsus]

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?

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

 

[Brandas]

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

 

[khaytsus]

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

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

 

[Synman]

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.

 

[giveen]

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

 

[nikoltu]

Maybe who try developing kernel should search help in other tegra2 device forums

Sent from my LG-P500 using Tapatalk

 

[EwanG]

Maybe who try developing kernel should search help in other tegra2 device forums

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

 

[giveen]

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