Hi,
I am trying to boot 2.6.13.4 kernel in an ixp425 machine. I am using a
proprietary bootloader that worked fine with 2.4 kernel. But there is a
problem with 2.6 kernel. I tried to debug a little using a jtag
debugger. The bootloader copies the zImage to a memory location (say,
0xXXXXX000) in the ram and jumps there. After that the PC is caught in
a loop 0xXXXXX62e - 0xXXXXX630 - 0xXXXXX634 - 0xXXXXX638 - 0xXXXXX62e
..... The image is not even umcompressed. Has anything changed from 2.4
to 2.6 kernel which requires the bootloaders to do something more/extra
(for arm architecture).
Re: kernel upgrade ... From the boot o/p you can see that the card is trying to send ... If I use kernel2.4 in the same configuration, the card boots up ...Uncompressing Kernel Image ... ... help me understand the relation of kernel to the bootloader.... (comp.os.linux.embedded)
Re: [PATCH] i386: handle an initrd in highmem (version 2) ... which makes the lowmem/highmem boundary visible to the boot... This was exported to the bootloader via a compile-time ... the vmalloc= command-line option breaks this ... lowmem boundary inside the kernel itself. ... (Linux-Kernel)
Re: Ramdisk support ...PXE bootloader for loading the kernel.... use it to boot FreeBSD before. ... (freebsd-hackers)
Re: [opensuse] device.map - Darryl/Carl/Boyd ... This allows menu.lst to remain as-is when the kernel is next updated. ... just 'sanity checking' your work before trying to boot......loader configuration module will update configuration files until the cows ... still no grub bootloader when the computer boots up. ... (SuSE)
Re: OMAP2420 Kernel Debugging problem ... OALKitlCreateName has been implemented specifically and in the bootloader... But for Kernel, the funtion in name.c is taken. ...Connecting to Desktop .. ... (microsoft.public.windowsce.platbuilder)
