Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: "Willem-Jan de Hoog" <wdehoog@exalondelft.nl>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
	"Linus Walleij" <linus.walleij@linaro.org>,
	"Florian Fainelli" <f.fainelli@gmail.com>
Cc: "Rafał Miłecki" <rafal@milecki.pl>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] nvmem: brcm_nvram: use buffered nvram data for cell values
Date: Tue, 7 Feb 2023 11:50:23 +0300	[thread overview]
Message-ID: <dca5d799-a562-4494-bbf4-79b7e9420cac@arinc9.com> (raw)
In-Reply-To: <cover.1675717472.git.wdehoog@exalondelft.nl>

On 7.02.2023 11:42, Willem-Jan de Hoog wrote:
> On OpenWrt 22.03.3, Asus RT-AC88U does not boot anymore:
> 
>    UBI: auto-attach mtd4
>    ubi0: attaching mtd4
>    ubi0 error: 0xc04f0b3c: PEB 0 contains corrupted VID header, and the
>       data does not contain all 0xFF
>    ubi0 error: 0xc04f0b4c: this may be a non-UBI PEB or a severe VID
>       header corruption which requires manual inspection
> 
> The problem seems to be that brcm_nvram_read accesses its (mapped) io
> memory. When doing so the correct data is read but after that the
> mtd/ubi process fails to work.
> 
> The bcm47xx_nvram.c code has buffered the nvram data so the cells value
> can be read from there.
> 
> v3:
> - Export symbol for modules.
> - No dependency on Kconfig.
> 
> v2:
> - Fix the wrong author information.
> 
> v1:
> - arinc.unal: Improved patch subject and log
> 
> Willem-Jan de Hoog (2):
>    The bcm47xx code makes a copy of the NVRAM data in ram. Allow access
>      to this data so property values can be read using nvmem cell api.
>    The bcm47xx module has a copy of the NVRAM data in ram. When available
>      use this one instead of reading from io memory since it causes
>      mtd/ubi to fail.

I believe you're supposed to put the subject of the patches here, keep 
that in mind for future contributions. No need to resubmit as this is 
just composition.

Arınç

       reply	other threads:[~2023-02-07  9:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1675717472.git.wdehoog@exalondelft.nl>
2023-02-07  8:50 ` Arınç ÜNAL [this message]
2023-02-08 10:17 ` [PATCH v3 0/2] nvmem: brcm_nvram: use buffered nvram data for cell values Arınç ÜNAL
     [not found] ` <e179c12f73a6035690e814b842f677bbb38f5c96.1675717472.git.wdehoog@exalondelft.nl>
2023-02-08 10:25   ` [PATCH v3 2/2] nvmem: brcm_nvram: use bcm47xx buffered data Rafał Miłecki
2023-02-08 10:29     ` Arınç ÜNAL
2023-02-08 10:45       ` Rafał Miłecki

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=dca5d799-a562-4494-bbf4-79b7e9420cac@arinc9.com \
    --to=arinc.unal@arinc9.com \
    --cc=f.fainelli@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=wdehoog@exalondelft.nl \
    --cc=zajec5@gmail.com \
    /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