How to compile your kernel (not using buildroot):
1. Build yourself a cross compiler for arm (little endian), you can use buildroot and the nspire-scripts.
Than add the binarys to your PATH (if they dont have a prefix like "arm-gcc", add one)
2. Create a new folder for your build
3. clone tangrs git tree with "git clone git://github.com/tangrs/linux" and "cd linux"
4. Download my patch (for X, directfb...) "wget http://dl.dropbox.com/u/105478372/fbdev.patch" and apply it "git apply fbdev.patch"
5. Edit "Makefile" and search for "ARCH ?= $(SUBARCH)" and change it to "ARCH := arm".
    Do the same for "CROSS_COMPILE ?= <something>" and change it to "CROSS_COMPILE := <your arm-gcc-prefix e.g. 'arm-elf-'>"
6. "make nspire_defconfig"
7. "make menuconfig", "make xconfig" or "make gconfig"
Configure it suitable for your needs, but enable (Search using "/"):
CONFIG_EXT4_FS
EXT4_USE_FOR_EXT23
CONFIG_SCSI
CONFIG_BLK_DEV_SD
CONFIG_USB_STORAGE
CONFIG_SWAP if you want to use swap
CONFIG_STRIP_ASM_SYMS if you dont want to debug the kernel
disable CONFIG_LOGO if you want to see longer errors on your screen without scrolling

For internet you will need:
CONFIG_INET
CONFIG_NETDEVICES
For WLAN:
CONFIG_CFG80211
CONFIG_MAC80211
and the driver for your WLAN-dongle, you can get the name with "lsusb -v".

If something doesn't work, there are many tutorials on configuring your kernel.
8. Compile: "make zImage -j"
9. Make cup of coffee
10. Drink it, but be careful, it may be hot
11. "mv arch/arm/boot/zImage zImage.tns"
12. Copy it onto your calculator
13. Boot

Here, the "build yourself" means for me to open emacs, and start coding. Is that what you wanted to say?

You could do that if you have the patience and time, but http://hackspire.unsads.com/wiki/index.php/C_and_assembly_development_introduction_on_Linux should be faster if you're not trying to compile it on a 4004
Your prefix will be arm-none-eabi-, you just have to copy the binarys created into /usr/bin, /opt/cross or whatever directory is in your $PATH.

Where you talking about the rule "some" and "tea"?

That'd be possible to, but the configuration is much more complicated..

floris, attached is the bootscript, remember that to run it you have to add the command to the ndless.cfg

hey vogtinator, theres something i dont understand, once i have everything you have and i want just to add a wifidongle driver, do i have to follow all the steps u posted?

one more thing, does that driver has to be in the rootfs or can i put it in the zimage.tns??


Regards...

nonono, i made that bootscipt, its like the bootscript of tangrs but tangrs doesnt have the initrd just the zimage

Quote

Here, the "build yourself" means for me to open emacs, and start coding. Is that what you wanted to say?

You could do that if you have the patience and time, but http://hackspire.unsads.com/wiki/index.php/C_and_assembly_development_introduction_on_Linux should be faster if you're not trying to compile it on a 4004
Your prefix will be arm-none-eabi-, you just have to copy the binarys created into /usr/bin, /opt/cross or whatever directory is in your $PATH.

Ah ! For sure I already have that.
But now imagine I have succesfuly compiled the kernel, how to compile stuff that is not included in that kernel ? (for example, how to you manage to add the extra-programs that are available by default when you run your kernel ?).
Maybe I've missed one post, but I cannot figure out how you're dealing with the *double* cross compiler (linux <> arm nspire <> arm linux).

Buildroot enables one to build and install a number of programs and libraries to a given location on the host disk, forming the target FS. The contents of that location are recursively compressed (for initrd), or can be recursively copied as is to external USB Mass Storage Device.
For other programs/libraries not directly provided by buildroot, just tell the build system of said programs/libraries that it should use an install prefix relative to the root of the target FS.

Provided the arm-none-eabi and arm-linux-gnueabi toolchains have different names, dealing with them requires nothing special.

But now imagine I have succesfuly compiled the kernel, how to compile stuff that is not included in that kernel ? (for example, how to you manage to add the extra-programs that are available by default when you run your kernel ?).

Ok, guide for buildroot:
1. "git clone git://git.buildroot.org/buildroot" and "cd buildroot"
2. "make menuconfig"
3. Target Architecture -> ARM (little endian)
4. Target Architecture Variant -> arm926t
5. Enable BR2_CCACHE for faster recompilings
6. System Configuration -> Port to run a getty (login prompt) on -> tty0
7. Configure what you want, but use GCC 4.6.x as 4.7 introduces some preprocessor bugs.
8. Edit system/skeleton/etc/passwd and change "root:x:0" to "root::0"
9. "make"
10. "tar -xvf output/images/rootfs.tar -C <usb-stick>"
11. boot
12. Play crysis if you chose to build it (may need some time)

Of course you can use whatever arm(v5) linux distro you like. But most of them are waaay to slow.