Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 10 May 2013 14:32:54 +0200 (CEST) Received: from mga09.intel.com ([134.134.136.24]:33673 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by eddie.linux-mips.org with ESMTP id S6822517Ab3EJMcuc1JUj (ORCPT ); Fri, 10 May 2013 14:32:50 +0200 Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 10 May 2013 05:30:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,647,1363158000"; d="scan'208";a="334828866" Received: from linux.jf.intel.com (HELO linux.intel.com) ([10.23.219.25]) by orsmga002.jf.intel.com with ESMTP; 10 May 2013 05:32:42 -0700 Received: from [10.237.72.153] (sauron.fi.intel.com [10.237.72.153]) by linux.intel.com (Postfix) with ESMTP id 905796A4087; Fri, 10 May 2013 05:32:31 -0700 (PDT) Message-ID: <1368189329.26780.157.camel@sauron.fi.intel.com> Subject: Re: [PATCH 0/3] fix NVRAM partition size if larger than expected From: Artem Bityutskiy Reply-To: dedekind1@gmail.com To: Jonas Gorski Cc: linux-mtd@lists.infradead.org, David Woodhouse , Maxime Bizon , Florian Fainelli , Kevin Cernekee , linux-mips@linux-mips.org Date: Fri, 10 May 2013 15:35:29 +0300 In-Reply-To: <1364044070-10486-1-git-send-email-jogo@openwrt.org> References: <1364044070-10486-1-git-send-email-jogo@openwrt.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 (3.6.4-3.fc18) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit 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: 36379 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: dedekind1@gmail.com 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 Sat, 2013-03-23 at 14:07 +0100, Jonas Gorski wrote: > Some device vendors use a larger nvram size than expected. While Broadcom > has defined it as 64K max, devices with 128K have been seen in the wild. > Luckily they properly set the nvram's PSI size to the correct value, so > we can use that to size the nvram partion. > > Yes it's a bit confusing as there are two nvrams, one with a fixed layout > with in the bootloader, with the size information about the other. > > Since 2 of 3 patches are for the mtd tree, this patchset should go there > (but it applies to both l2-mtd and mips-next fine). Pushed all 3 to l2-mtd.git, thanks! -- Best Regards, Artem Bityutskiy