From: Artem Bityutskiy <dedekind1@gmail.com>
To: Jonas Gorski <jogo@openwrt.org>
Cc: linux-mips@linux-mips.org, Kevin Cernekee <cernekee@gmail.com>,
linux-mtd@lists.infradead.org, Maxime Bizon <mbizon@freebox.fr>,
David Woodhouse <dwmw2@infradead.org>,
Florian Fainelli <florian@openwrt.org>
Subject: Re: [PATCH 0/3] fix NVRAM partition size if larger than expected
Date: Fri, 10 May 2013 15:35:29 +0300 [thread overview]
Message-ID: <1368189329.26780.157.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1364044070-10486-1-git-send-email-jogo@openwrt.org>
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
prev parent reply other threads:[~2013-05-10 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 13:07 [PATCH 0/3] fix NVRAM partition size if larger than expected Jonas Gorski
2013-03-23 13:07 ` [PATCH 1/3] MTD: bcm63xxpart: use size macro for CFE block size Jonas Gorski
2013-03-23 13:07 ` [PATCH 2/3] MIPS: BCM63XX: export PSI size from nvram Jonas Gorski
2013-03-23 13:39 ` Florian Fainelli
2013-05-10 12:36 ` Artem Bityutskiy
2013-05-12 10:48 ` Jonas Gorski
2013-05-12 14:52 ` Florian Fainelli
2013-03-23 13:07 ` [PATCH 3/3] MTD: bcm63xxpart: use nvram for PSI size Jonas Gorski
2013-03-23 13:39 ` [PATCH 0/3] fix NVRAM partition size if larger than expected Florian Fainelli
2013-05-10 12:35 ` Artem Bityutskiy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1368189329.26780.157.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=dwmw2@infradead.org \
--cc=florian@openwrt.org \
--cc=jogo@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mbizon@freebox.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).