linux-kernel - Re: [PATCH] of: specify initrd location using 64-bit

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

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5050CE33.9060909@ti.com>
Date:	Wed, 12 Sep 2012 14:02:27 -0400
From:	Cyril Chemparathy <cyril@...com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
CC:	<devicetree-discuss@...ts.ozlabs.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-c6x-dev@...ux-c6x.org>, <linux-kernel@...r.kernel.org>,
	<linux-mips@...ux-mips.org>, <linux@...nrisc.net>,
	<linuxppc-dev@...ts.ozlabs.org>,
	<microblaze-uclinux@...e.uq.edu.au>, <a-jacquiot@...com>,
	<arnd@...db.de>, <benh@...nel.crashing.org>,
	<bigeasy@...utronix.de>, <blogic@...nwrt.org>,
	<david.daney@...ium.com>, <dhowells@...hat.com>,
	<grant.likely@...retlab.ca>, <hpa@...or.com>, <jonas@...thpole.se>,
	<linus.walleij@...aro.org>, <linux@....linux.org.uk>,
	<m.szyprowski@...sung.com>, <mahesh@...ux.vnet.ibm.com>,
	<mingo@...hat.com>, <monstr@...str.eu>, <msalter@...hat.com>,
	<nico@...aro.org>, <paul.gortmaker@...driver.com>,
	<paulus@...ba.org>, <ralf@...ux-mips.org>,
	<rob.herring@...xeda.com>, <suzuki@...ibm.com>,
	<tglx@...utronix.de>, <tj@...nel.org>, <x86@...nel.org>
Subject: Re: [PATCH] of: specify initrd location using 64-bit

On 9/12/2012 12:16 PM, Geert Uytterhoeven wrote:
> On Wed, Sep 12, 2012 at 6:05 PM, Cyril Chemparathy <cyril@...com> wrote:
>> On some PAE architectures, the entire range of physical memory could reside
>> outside the 32-bit limit.  These systems need the ability to specify the
>> initrd location using 64-bit numbers.
>>
>> This patch globally modifies the early_init_dt_setup_initrd_arch() function to
>> use 64-bit numbers instead of the current unsigned long.
>
>> -void __init early_init_dt_setup_initrd_arch(unsigned long start, unsigned long end)
>> +void __init early_init_dt_setup_initrd_arch(u64 start, u64 end)
>
> Why not phys_addr_t?
>

The rest of the memory specific bits of the device-tree code use u64 for 
addresses, and I kept it the same for consistency.

> Gr{oetje,eeting}s,
>
>                          Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                  -- Linus Torvalds
>

-- 
Thanks
- Cyril
--
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/