#13284: ARM image installer
----------------------------+----------------------------
Reporter: kallisti5 | Owner: bonefish
Type: enhancement | Status: new
Priority: low | Milestone: Unscheduled
Component: Build System | Version: R1/Development
Resolution: | Keywords: arm
Blocked By: | Blocking:
Has a Patch: 0 | Platform: arm
----------------------------+----------------------------
Comment (by pulkomandy):
I wouldn't count on a common memory map on the physical side. I think even
with raspberry pi + beagle xM, we already have no overlapping RAM areas.
However, this does not matter to our kernel. Our kernel starts with MMU
already enabled and it is mapped in 0x80000000. This address is fixed (it
is opposite to Linux where the kernel side starts at 0 and userland at
80000000).
The work to get that set up is in haiku_loader. It is the one that enables
the mmu and maps the kernel at the appropriate place.
So, the kernel is not a problem. The FDT can be used to discover hardware,
etc.
What we need to do is either:
- Write a custom haiku_loader for each board (annoying, but easy)
- Write an haiku_loader that can figure out by itself a way to perform
that mmu mapping, depending on the physical RAM layou (more work, but more
generic).
Unless the plan is now to remove haiku_loader and use u-boot to load the
kernel directly? I'm not sure that's the way to go, as we would loose our
nice boot menu with blacklist packages, booting old system versions, etc.
--
Ticket URL: <https://dev.haiku-os.org/ticket/13284#comment:6>
Haiku <https://dev.haiku-os.org>
Haiku - the operating system.
