Hi Kevin, On Fri, Feb 13, 2009 at 8:31 PM, Kevin O'Connor <[email protected]> wrote:
> 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. Of course, that's why I'm porting it and have created a temporary mach-type id ;-) The reason I'm copying the Dell Axim x50 code is that both devices use the same processor, the pxa270, and the pxa270 has an integrated LCD controller, so I don't need to worry about determining where they might exist with GPIO - assuming that my device has opted to use the integrated lcd controller and not GPIO. I've ported several (arm) machines to Linux-2.6 already, but this is really my first where there is no rs232 port. Historically, they've all been SBCs. >> 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. #define PHYSOFFSET_KERNEL 0x8000 So RAMADDR + PHYSOFFSET_KERNEL is the location of the zImage _after_ it has been copied by the preloader in linboot.cpp, correct? In my case, that's 0xa0008000, so I'm assuming this to be my zreladdr (it's the default anyway). #define PHYSOFFSET_TAGS 0x100 So RAMADDR + PHYSOFFSET_TAGS is the location of the atags structure _after_ it has been copied by the preloader in linboot.cpp, correct? In my case, that's 0xa0000100 ... so I'm guessing that I should set the .boot_params member to that in my MACHINE_START(). Incidentally, do you have any tips for getting the fb console working? My display is QVGA 240x320 ... HaRET reports where the video ram starts, but does it also have the size somewhere? ... I'm just asking because I have no console at all, and thought that might be fixed if i were to set video_start and video_end in MACHINE_START. Thanks for your help, Cheers, Chris _______________________________________________ Haret mailing list [email protected] https://handhelds.org/mailman/listinfo/haret
