How to build uimage from my kernel linux-2.6.10_mvl401 ,then need to port on my arm PXA 300 through TFTP .
What all steps I require to do.In which configuration file i should make changes for ethernet for boot

You haven't really given enough detail to give a concise answer. However, reading between the lines, it sounds like you need to cross-compile and kernel, and then use a boot host to load the kernel in the target using something like PXE.
If so, to build the kernel you will need the kernel sources and cross toolchain that runs on your build host and that is targeted to the particular ARM CPU of your PXA 300. Do you have those?
I isn't clear what you mean by 'port on my ARM through TFTP'. Normally, when TFTP is used, it is to boot a diskless host using only a network. Usually/sometimes, TFTP is used in conjunction with DHCP and a PXE bootloader. Is that what you mean?

--- rod.

I have a PXA 300 board in which I have load uboot. I have a monta vista 4 kernel (linux-2.6.10_mvl401).I need to build the uImage from that kernel(linux-2.6.10_mvl401) ,that uImage I need to port in my PXA 300 board arm processor through ethernet( I have TFTP software to load uImage) .
monta vista 4 kernel (linux-2.6.10_mvl401) supports the PXA300 board .
My Question are
-How should I build uImage from kernel (as I know uImage is built by kernel only).Does It requires uboot also.Since I have load uboot on my target board (PXA)
-U asked about the kernel & cross compiler ,Kernel I have but which cross compiler I require.
-DO I have to configure kernel on ethernet side also .Since ill be loading uImage through tftp software.

Okay, since you haven't really added any information, I will conclude that my original assumptions were correct.
You need a compiler that is compatible with the ARM processor on your PXA target host. This compiler can either run natively on the target host, or can run on a different architecture which we call a build host. If the latter case, then the compiler is called a cross compiler. It sounds like this is the case that applies to you.
If your build host is a conventional Linux PC, then you may be able to acquire a compatible cross toolchain (compiler plus all related software development tools) from the vendor of the target host. If not, you will probably have to build one. To build a cross toolchain, I recommend the use of the crosstool-NG package. You can install crosstool-NG on the build host, and use it to generate a cross toolchain. The cross toolchain can then be used on the build host to build a kernel (and other software) to be run on your target host.
You build the uImage by configuring the kernel build system to use your cross toolchain, and then run 'make uImage' (grotesquely over-simplified recipe). Building kernels is fully independent of any bootloader.
I don't understand what you mean by 'DO I have to configure kernel on ethernet side also'. You will have to configure your kernel to include appropriate drivers for the ethernet hardware on your target board. This is completely independent of what mechanism is used to copy the uImage to the target host.
It isn't clear whether you are asking about booting the new kernel as a diskless host, or whether you want to simply copy the kernel image to some kind of storage on the target host. Since you seem to have a bootloader on the target host, I will guess that it also has local storage. You would normally not use something as primitive as TFTP to copy files from one host to another, although I suppose if that is all you have, then that's what you would do.
Do you have a working kernel and root filesystem on your PXA300 target host, or do you intend to bring up a completely new kernel and other OS components from scratch? If the latter, then I feel compelled to advise you that given your current knowledge level, you should be prepared to spend a good deal of time and effort to accomplish your task.

--- rod.

Thanks for reply

Yes I have cross compiler(arm-linux-4.1.1) that is compatiable for my board target.

Actually this board is already used for fedora kernel & initrd which is working fine .Now we have to bring up this same board for montavista (kernel 2.6.10) .Ya bootloader is not a problem u-boot is working fine .

How should I do that

What I was thinking that to port uimage & initrd on target I need to configure Ethernet ( I WAS WRONG ) . THis will be done by u-boot itself. so I need not to bother

Look in the kernel Makefile. You should find a section where the variable 'CROSS_COMPILE' is defined. Set the values of 'ARCH' to 'arm' (or possibly some variant like 'arm-v4') and 'CROSS_COMPILE' to the file filesystem path of your cross compiler. The name it expects is the full filename, with the suffix 'gcc' removed. For example, if your compiler is installed as
then the form expected in the Makefile would be
Make will fill in the rest, including for other elements of your toolchain.

The variables can also be assigned on the make commandline.


EDIT:

Better: just use the menuconfig kernel Makefile target to select all options for building the new kernel.
--- rod.

Okay, now I have to eat my words, and a bit of crow. I guess it turns out that the uImage format is specific to U-boot bootloaders, and requires some sort of utility 'mkimage' to build the compressed kernel image. I assume that this is available somewhere; wherever U-boot is provided. Maybe you already have it; I don't.
Sorry for jumping to the wrong conclusion that kernel building is fully independent of bootloaders. I incorrectly assumed that the uImage format was some flavor of the day for compressed images; one I'd not previously heard of.

--- rod.