From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Sat, 20 Jul 2013 14:22:53 +0200 (CEST) Received: from mail-wi0-f182.google.com ([209.85.212.182]:60726 "EHLO mail-wi0-f182.google.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S6819547Ab3GTMWsfsjM1 (ORCPT ); Sat, 20 Jul 2013 14:22:48 +0200 Received: by mail-wi0-f182.google.com with SMTP id m6so517920wiv.3 for ; Sat, 20 Jul 2013 05:22:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:from:subject:to:cc:in-reply-to:references:date:message-id :x-gm-message-state; bh=XcdXracHRIgimbtu8T9qLQjEqC1u44dVNmZNhfb2zZc=; b=Xzv/DHI+8xdMbPoT5KRAwqOO6Si8F9BZOIp1eG0chYmnbuuMj5s2hfBcIJkIE6Tp7u GwD6i8JR3YK906dv46BkdMJqor6F2Co6kI9aLjqd+LKd04Fwk5Uj9AHjknw3Skx/clgz Cq23xAsccW6IJjr29xSqU2qL836SGAi2xnI18L3cqgPYBa1XFfUOM59es9lVVIRhwS2C uDxYQck00fLSqMhnMhX4atev2wOgZAaZE5M2JCqPBDEb7HvxW06ivf/Rxy1lPF1t62pV uOGQ9D5DG09njlj8vFXQXrqf26lna210K8LN5hs9bY0mNBXqzKwMFUR1jLUFCwgMVyYh 6Sag== X-Received: by 10.180.211.202 with SMTP id ne10mr13976194wic.39.1374322962843; Sat, 20 Jul 2013 05:22:42 -0700 (PDT) Received: from localhost (dab-bhx1-h-1-2.dab.02.net. [82.132.228.222]) by mx.google.com with ESMTPSA id fd3sm54041091wic.10.2013.07.20.05.22.39 for (version=TLSv1.1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 20 Jul 2013 05:22:41 -0700 (PDT) Received: by localhost (Postfix, from userid 1000) id C7AC63E0C52; Fri, 19 Jul 2013 22:39:45 -0700 (PDT) From: Grant Likely Subject: Re: [PATCH v2] of: Specify initrd location using 64-bit To: Rob Herring , Santosh Shilimkar Cc: Rob Herring , Geert Uytterhoeven , Sebastian Andrzej Siewior , Jean-Christophe PLAGNIOL-VILLARD , Vineet Gupta , Russell King , Catalin Marinas , Will Deacon , Mark Salter , Aurelien Jacquiot , James Hogan , Michal Simek , Ralf Baechle , Jonas Bonn , Benjamin Herrenschmidt , Paul Mackerras , x86@kernel.org, arm@kernel.org, Chris Zankel , Max Filippov , Nicolas Pitre , linux-arm-kernel@lists.infradead.org, linux-c6x-dev@linux-c6x.org, linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org, linux-xtensa@linux-xtensa.org, devicetree-discuss@lists.ozlabs.org In-Reply-To: <51D1F5E2.6070609@gmail.com> References: <1372702835-5333-1-git-send-email-santosh.shilimkar@ti.com> <51D1F5E2.6070609@gmail.com> Date: Sat, 20 Jul 2013 06:39:45 +0100 Message-Id: <20130720053945.C7AC63E0C52@localhost> X-Gm-Message-State: ALoCoQm/K43/6HzALS48mveYhOuqpq66Tu66wkLB3IrH6JO2mTIn7bQ+j/UUO8Dy1HUycyrR7B6d Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 37337 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: grant.likely@linaro.org Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote: > On 07/01/2013 01:20 PM, Santosh Shilimkar 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. > > > > There has been quite a bit of debate about whether to use u64 or phys_addr_t. > > It was concluded to stick to u64 to be consistent with rest of the device > > tree code. As summarized by Geert, "The address to load the initrd is decided > > by the bootloader/user and set at that point later in time. The dtb should not > > be tied to the kernel you are booting" > > That was quoting me. Otherwise: > > Acked-by: Rob Herring > > Unless Grant feels compelled to pick this up for 3.11, I think it has to > wait for 3.12. Nope, 3.12 is fine. Applied. g. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (not verified)) by ozlabs.org (Postfix) with ESMTPS id E1D482C00A2 for ; Sat, 20 Jul 2013 22:22:46 +1000 (EST) Received: by mail-wg0-f43.google.com with SMTP id z11so4573663wgg.34 for ; Sat, 20 Jul 2013 05:22:42 -0700 (PDT) Sender: Grant Likely From: Grant Likely Subject: Re: [PATCH v2] of: Specify initrd location using 64-bit To: Rob Herring , Santosh Shilimkar In-Reply-To: <51D1F5E2.6070609@gmail.com> References: <1372702835-5333-1-git-send-email-santosh.shilimkar@ti.com> <51D1F5E2.6070609@gmail.com> Date: Sat, 20 Jul 2013 06:39:45 +0100 Message-Id: <20130720053945.C7AC63E0C52@localhost> Cc: Nicolas Pitre , linux-mips@linux-mips.org, Aurelien Jacquiot , Catalin Marinas , Sebastian Andrzej Siewior , Will Deacon , Max Filippov , Paul Mackerras , Jonas Bonn , Russell King , linux-c6x-dev@linux-c6x.org, x86@kernel.org, arm@kernel.org, Geert Uytterhoeven , Mark Salter , Jean-Christophe PLAGNIOL-VILLARD , linux-xtensa@linux-xtensa.org, James Hogan , devicetree-discuss@lists.ozlabs.org, Rob Herring , linux-arm-kernel@lists.infradead.org, Chris Zankel , Michal Simek , Vineet Gupta , Ralf Baechle , linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote: > On 07/01/2013 01:20 PM, Santosh Shilimkar 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. > > > > There has been quite a bit of debate about whether to use u64 or phys_addr_t. > > It was concluded to stick to u64 to be consistent with rest of the device > > tree code. As summarized by Geert, "The address to load the initrd is decided > > by the bootloader/user and set at that point later in time. The dtb should not > > be tied to the kernel you are booting" > > That was quoting me. Otherwise: > > Acked-by: Rob Herring > > Unless Grant feels compelled to pick this up for 3.11, I think it has to > wait for 3.12. Nope, 3.12 is fine. Applied. g. From mboxrd@z Thu Jan 1 00:00:00 1970 From: grant.likely@linaro.org (Grant Likely) Date: Sat, 20 Jul 2013 06:39:45 +0100 Subject: [PATCH v2] of: Specify initrd location using 64-bit In-Reply-To: <51D1F5E2.6070609@gmail.com> References: <1372702835-5333-1-git-send-email-santosh.shilimkar@ti.com> <51D1F5E2.6070609@gmail.com> Message-ID: <20130720053945.C7AC63E0C52@localhost> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote: > On 07/01/2013 01:20 PM, Santosh Shilimkar 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. > > > > There has been quite a bit of debate about whether to use u64 or phys_addr_t. > > It was concluded to stick to u64 to be consistent with rest of the device > > tree code. As summarized by Geert, "The address to load the initrd is decided > > by the bootloader/user and set at that point later in time. The dtb should not > > be tied to the kernel you are booting" > > That was quoting me. Otherwise: > > Acked-by: Rob Herring > > Unless Grant feels compelled to pick this up for 3.11, I think it has to > wait for 3.12. Nope, 3.12 is fine. Applied. g. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grant Likely Subject: Re: [PATCH v2] of: Specify initrd location using 64-bit Date: Sat, 20 Jul 2013 06:39:45 +0100 Message-ID: <20130720053945.C7AC63E0C52@localhost> References: <1372702835-5333-1-git-send-email-santosh.shilimkar@ti.com> <51D1F5E2.6070609@gmail.com> Return-path: In-Reply-To: <51D1F5E2.6070609@gmail.com> Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: Rob Herring , Santosh Shilimkar Cc: Rob Herring , Geert Uytterhoeven , Sebastian Andrzej Siewior , Jean-Christophe PLAGNIOL-VILLARD , Vineet Gupta , Russell King , Catalin Marinas , Will Deacon , Mark Salter , Aurelien Jacquiot , James Hogan , Michal Simek , Ralf Baechle , Jonas Bonn , Benjamin Herrenschmidt , Paul Mackerras , x86@kernel.org, arm@kernel.org, Chris Zankel , Max Filippov , Nicolas List-Id: devicetree@vger.kernel.org On Mon, 01 Jul 2013 16:34:26 -0500, Rob Herring wrote: > On 07/01/2013 01:20 PM, Santosh Shilimkar 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. > > > > There has been quite a bit of debate about whether to use u64 or phys_addr_t. > > It was concluded to stick to u64 to be consistent with rest of the device > > tree code. As summarized by Geert, "The address to load the initrd is decided > > by the bootloader/user and set at that point later in time. The dtb should not > > be tied to the kernel you are booting" > > That was quoting me. Otherwise: > > Acked-by: Rob Herring > > Unless Grant feels compelled to pick this up for 3.11, I think it has to > wait for 3.12. Nope, 3.12 is fine. Applied. g.