On Fri, Feb 13, 2009 at 05:15:00PM -0500, Christopher Friedt wrote: > According to the list, this seems to be the prevailing problem for > people who start using HaRET. > > Most people can easily copy over the kernel image, initrd, and > default.txt files using ActiveSync, but running leaves them with > output like this[1].
The main issue here is that ARM machines are not generic like X86 machines are. Each individual device requires a custom kernel - one can not assume that a similar device will work with the same kernel. What you're seeing at [1] is (generally) haret successfully handing control off to the linux kernel. There isn't anything haret can do here to improve the situation - as haret isn't even running anymore. To improve debugging, you'll need to bring up suggestions with the linux kernel developers. > In my case, I'm using HaRET to port Linux to new machine (undisclosed > at the moment). It's based on a PXA270 processor, and I assumed that > it would be easy to just copy the Dell Axim X50 kernel code and modify > it slightly, since the Axim X50 has already been ported to Linux with > HaRET. What I did, was copy the X50 source, renamed most of the > functions and data structures, and then defined my own entry in > arm/asm/tools/mach-types. > > This line is particularly interesting, showing virtual/physical addresses: > > Allocated 279 pages (tags=49900000/a74a5000 kernel=49901000/a74a4000 > initrd=49A13000/a7392000 index=49A13000/a7392000) > > The kernel is loaded at 0xa74a4000 ... is this number related to the > zreladdr defined in arch/arm/mach-pxa/Makefile.boot ? No. Those addresses are temporary addresses that are allocated under wince. The preloader() function in src/linboot.cpp copies the data from the temporary locations to the permanent locations. For the permanent memory locations, see the definitions of PHYSOFFSET_* in src/linboot.cpp. -Kevin _______________________________________________ Haret mailing list [email protected] https://handhelds.org/mailman/listinfo/haret
