Dear Stephen Warren, In message <74cdbe0f657a3d45afbb94109fb122ff173a2c7...@hqmail01.nvidia.com> you wrote: > > > > OK. Wouldn't we also need e.g. IH_TYPE_STANDALONE_REL, IH_TYPE_RAMDISK_REL > > > and perhaps other too? > > > > I don't think so - either these don't have (and use) load and entry > > point addesses (like in the ramdisk case), or they are not easily > > relocatable in the same way as the Linux kernel. > > Sorry, I don't quite understand then; in both boot_get_ramdisk() and > boot_get_fdt(), I see calls to image_get_load() and fit_image_get_load().
Agreed for FDT images, but you wrote IH_TYPE_STANDALONE_REL - standanole images are something differend, and usually not relocatable. And ramdisks have neither a load address nor an entry point associated with them; no matter where they are located in memory, we just pass their address to the Linux kernel. > I guess in the ramdisk case, this just sets rd_load, which isn't used, > but in the FDT case, it sets load_start, which is used to derive load_end > and fdt_blob. Agreed. But that's not what you wrote above. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de "There's only one way to have a happy marriage and as soon as I learn what it is I'll get married again." - Clint Eastwood _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
