|To:||Chris Boot <firstname.lastname@example.org>|
|Subject:||Re: Execute-in-Place (XIP)|
|From:||David Daney <email@example.com>|
|Date:||Fri, 28 Oct 2005 16:08:08 -0700|
|References:||<18E0376E-A524-42EE-A5ED-BDF9A0668DE6@bootc.net> <20051027102912.GB17645@linux-mips.org> <942B8B78-5F73-4647-AAA6-6025EABEDD1E@bootc.net> <6D27C791-80C1-42BA-8874-D117DC188F5C@bootc.net>|
|User-agent:||Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929)|
Chris Boot wrote:
Now, who knows how much initialisation a bootloader is expected to perform? Does the vrboot loader do the necessary operations, in which case I can just work on that instead of writing my own?
It depends. Depending on the hardware: Initialize clocks (things like PLL divisors and such). Initialize serial port so it can report on its progress. Initialize memory controller (so that RAM functions).(optionally) copy bootmonitor to ram so that it can run out of cached memory.
(optionally) copy kernel image to ram (possibley uncompressing it) and transfersing control to the kernel.
If you are doing XIP, the last two steps are probably skipped.I have no idea what the vrboot loader does, but that is what the Xilleon boot loaders do.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Execute-in-Place (XIP), Chris Boot|
|Next by Date:||Re: Linux-2.6.12 code base for linux-mips, Stuart Longland|
|Previous by Thread:||Re: Execute-in-Place (XIP), Chris Boot|
|Next by Thread:||[PATCH] vr41xx: add plat_setup to -mm queue, Yoichi Yuasa|
|Indexes:||[Date] [Thread] [Top] [All Lists]|