Optimizing Linux on ARM920T (MXL from Freescale)

Hi all,

I just started to develop Linux OS for arm920t processor.
I want to build very simple and quick kernel, because I need real-time
operations.
I have compiled 2.6.23 kernel (XIP, 1.1MB), have wrotten simple bootloader
(1.5KB). I use uClibc and buildroot toolchain.
I want to start linux kernel as quick as possible after power on (less
that 1s is wanted).
I will disable console, will run kernel and apps from ROM, will use
ramdisk and kernel modules. I will remove all stuff from kernel (minimal
networking, SLOB alocator, minimal dvivers and libraries).

What more optimizations ant simplifications can I made?
It is possible to build single user kernel?
Does anyone have experience with Linux on i.MXL processors?
All info and help welcome!

[LT] CodeC wrote:
> Hi all,
> 
> I just started to develop Linux OS for arm920t processor.
> I want to build very simple and quick kernel, because I need real-time
> operations.
> I have compiled 2.6.23 kernel (XIP, 1.1MB), have wrotten simple bootloader
> (1.5KB). I use uClibc and buildroot toolchain.
> I want to start linux kernel as quick as possible after power on (less
> that 1s is wanted).
> I will disable console, will run kernel and apps from ROM, will use
> ramdisk and kernel modules. I will remove all stuff from kernel (minimal
> networking, SLOB alocator, minimal dvivers and libraries).
> 
> What more optimizations ant simplifications can I made?
> It is possible to build single user kernel?
> Does anyone have experience with Linux on i.MXL processors?
> All info and help welcome!
> 
> 

A useful method to see where the kernel spends its cycles during booting 
is to pass the "initcall_debug" cmdline parameter, and enable the
CONFIG_PRINTK_TIME option in the configuration.

On Fri, 04 Jan 2008 09:31:31 -0600, "[LT] CodeC" <augulis.darius@gmail.com>
wrote:

>What more optimizations ant simplifications can I made?
>It is possible to build single user kernel?
>Does anyone have experience with Linux on i.MXL processors?
>All info and help welcome!

Just as an embedded RTOS Linux is rather fat. You might consider other
alternatives like eCos, rtems, FreeRTOS, ... These are designed for minimal
resource usage, so you may push down memory requirements for the whole
system to 256k or below, depend&#4294967295;ng on you application.

Mit freundlichen Gr&#4294967295;&#4294967295;en

Frank-Christian Kr&#4294967295;gel