| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTikoZDR2pCLT8RcS8S03QU1J8cTcDjZzc6ct+QUi@mail.gmail.com> Date: Tue, 22 Feb 2011 21:35:30 -0700 From: Grant Likely <grant.likely@...retlab.ca> To: Nicolas Pitre <nicolas.pitre@...aro.org> Cc: lkml <linux-kernel@...r.kernel.org>, linux-arm-kernel@...ts.infradead.org, Russell King <linux@....linux.org.uk> Subject: Re: [PATCH v4 7/7] dt: add documentation of ARM dt boot interface On Tue, Feb 22, 2011 at 7:55 PM, Nicolas Pitre <nicolas.pitre@...aro.org> wrote: > On Tue, 22 Feb 2011, Grant Likely wrote: > >> +The boot loader must load a device tree image (dtb) into system ram >> +at a 64bit aligned address and initialize it with the boot data. > [...] >> + r2 : physical pointer to the device-tree block >> + (defined in chapter II) in RAM. Device tree can be located >> + anywhere in system RAM, but it should be aligned on a 32 bit >> + boundary. > > So... which one is true? Oops, I thought I fixed that. It should be 64 bit boundary (actually, 32 bit is probably just fine, but there are some header fields which are u64 physical address values so it probably makes sense to keep it aligned for 64 bits). g. > > > Nicolas > -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists