<div>Hi at all<br><br><br>Since two week I have this Problem and can't solve it. I allready read DULG and search in<br>Mailinglists but I can't run linux. Perhaps had the same problem and can help me.<br>My Problem:<br>After I load the uImage (uImage at 0x00400000 )
<br>from server, I try to run in with command bootm.<br>=> bootm 00400000<br> Booting image at 00400000...<br> Image Name: Linux-2.4.24-pre2<br> Created: 2006-01-19 6:25:03 UTC<br> Image Type: PowerPC Linux Kernel Image (gzip compressed)
<br> Data Size: 700730 Bytes = 684.3 kB<br> Load Address: 00000000<br> Entry Point: 00000000<br> Verifying Checksum ... OK<br> Uncompressing Kernel Image ... OK</div>
<div> </div>
<div> don't start kernel </div>
<div> my board :<br> sdram 16m 0----ffffff</div>
<div> flash 4m ffc00000 ---fffffff<br> </div>
<div>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">routing, so my current assumption is<br>that I either have VIRTEX_UART defined improperly or I have the ppc_sys
<br>data structure created wrong.<br><br><br>><br>><br><br> It would be really nice if the was either some comments in<br>xparameters.h or in the Documents directory explaining what the Linux<br>xparameters values are so that it it would be easy to know what items
<br>from xparameters_xxx.h have to be mapped or redefined.<br><br><br><br>> This really isn't a big deal anyway; most of this discussion will become<br>> moot in short order. Sometime in the next few releases, linuxppc will
<br>> flip over to using a flattened device tree to pass device information<br>> from the boot loader to the kernel. xparameters will drop out of the<br>> kernel proper entirely except for the edk-generated device drivers
<br>> (which is another issue entirely). All the xparam stuff will be<br>> extracted into a device tree by u-boot or the zImage wrapper. The<br>> kernel just won't care. :)<br> Where can we get more information on what is happening here ?
<br>I started the E12 port with most info in xparameters, but I have been<br>moving towards getting things passed in board_info. I am not using<br>u-boot as the E12 has a general purpose elf loader, and it was easier to<br>
add a fee lines for Linux. Regardless I would like to be compatible with<br>whatever is coming - maybe even ahead fo the curve. The e12 is just the<br>first of a family of products - the e14 already exists. There maybe<br>
revisions of each at different speeds with different memory.<br><br><br>_______________________________________________<br>Linuxppc-embedded mailing list<br><a href="mailto:Linuxppc-embedded@ozlabs.org">Linuxppc-embedded@ozlabs.org
</a><br><a href="https://ozlabs.org/mailman/listinfo/linuxppc-embedded">https://ozlabs.org/mailman/listinfo/linuxppc-embedded</a><br></blockquote></div><br>