Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1304702
| From | Masahiro Yamada <yamada.masahiro@socionext.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Question] Any restriction for the location of initramdisk? |
| Date | 2016-01-08 17:20 +0100 |
| Message-ID | <qOHVF-HA-29@gated-at.bofh.it> (permalink) |
| References | <qOzv3-3m3-1@gated-at.bofh.it> <qOCsX-5li-43@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Jon, 2016-01-08 19:22 GMT+09:00 Jon Medhurst (Tixy) <tixy@linaro.org>: > On Fri, 2016-01-08 at 16:16 +0900, Masahiro Yamada wrote: >> Hi. >> >> >> I know DTB should be located within the reach of the kernel >> so that the kernel can get access to it at the early boot stage. >> In other words, DTB should be put in the low memory area. >> >> Does initramdisk has the similar restriction? > > I assume so, as that's what Documentation/arm/Booting says ... > > > 5. Load initramfs. > ------------------ > > Existing boot loaders: OPTIONAL > New boot loaders: OPTIONAL > > If an initramfs is in use then, as with the dtb, it must be placed in > a region of memory where the kernel decompressor will not overwrite it > while also with the region which will be covered by the kernel's > low-memory mapping. > > A safe location is just above the device tree blob which itself will > be loaded just above the 128MiB boundary from the start of RAM as > recommended above. Uh, the document states that clearly. Thanks! -- Best Regards Masahiro Yamada
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[Question] Any restriction for the location of initramdisk? Masahiro Yamada <yamada.masahiro@socionext.com> - 2016-01-08 08:20 +0100
Re: [Question] Any restriction for the location of initramdisk? "Jon Medhurst (Tixy)" <tixy@linaro.org> - 2016-01-08 11:30 +0100
Re: [Question] Any restriction for the location of initramdisk? Masahiro Yamada <yamada.masahiro@socionext.com> - 2016-01-08 17:20 +0100
csiph-web