On Fri, Jan 18, 2008 at 12:07:31AM -0500, Pavel Roskin wrote: > > On Wed, 2008-01-16 at 23:51 +0100, Robert Millan wrote: > > On Wed, Jan 16, 2008 at 04:52:46PM -0500, Pavel Roskin wrote: > > > > > > It seems to me that Linux uses "#size-cells" and "#address-cells" (see > > > drivers/of/base.c and arch/powerpc/kernel/prom_parse.c) > > > > We use "#size-cells" and "#address-cells" too, but they aren't useful by > > themselves. They describe the layout of /memory/available. > > > > See kern/powerpc/ieee1275/openfw.c:grub_available_iterate() > > As I understand, Linux uses "ranges", although it's hard to be sure. > There are many references to "ranges" in Linux sources under > arch/powerpc, although many of them are pertinent to buses rather than > to the system memory. Open Hack'Ware provides "ranges" for the memory.
/memory/available is organized in ranges (address, whose length is described by #address-cells, and size, whose length is described by #size-cells). Is that what you mean? > As for yaboot, it uses "claim" both for its needs and for loading the > kernel. And that's probably what GRUB could do. It is: loader/powerpc/ieee1275/linux.c: found_addr = grub_claimmap (linux_addr, linux_size); loader/powerpc/ieee1275/multiboot2.c: rc = grub_claimmap (phdr->p_paddr, phdr->p_memsz); -- Robert Millan <GPLv2> I know my rights; I want my phone call! <DRM> What use is a phone call… if you are unable to speak? (as seen on /.) _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
