<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.3806.1700" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#f4f7f7>
<DIV><FONT face=Arial size=2>Hi all,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>We're trying to make Linux run on our DBPXA based
platform. U-boot works fine, we can communicate through serial line with it,
using Minicom or HyperTerminal.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The kernel and file system image (u-boot multi
image) is loaded into RAM with kermit at 0xa3100000. But, when we try to
boot linux with the bootm command, it stops at "Starting Kernel" (We're working
with Linux kernel 2.4.19 patched with -rmk7-pxa1 in eLinOS distribution).
</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>In order to see if something went wrong, we've
compared vmlinux.bin before compression and the kernel decompressed in RAM, in
position Load_address. We've found that the information is the same but one is
in big endian (in RAM) and the other one in little endian (vmlinux.bin). The
platform works in little endian, so this is probably the problem. How can we
solve it?? Is it a gunzip problem?? </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Thanks in advance</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Best regards,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Sonia</FONT></DIV></BODY></HTML>