All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Hutchinson <b.hutchman@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114
Date: Mon, 8 Nov 2021 07:55:00 -0500	[thread overview]
Message-ID: <CAFZh4h-1famKHUGPxAr7fvT7mFu5rv7ecG-5TWj9nSa-Y+LFOA@mail.gmail.com> (raw)
In-Reply-To: <CAOMZO5B4dv3Jp_UU9bdqMLeLL1OTy+W6v58MrkJavREzmdmGXQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

Hi Fabio,

On Mon, Nov 8, 2021 at 5:49 AM Fabio Estevam <festevam@gmail.com> wrote:

> Hi Brian,
>
> On Mon, Nov 8, 2021 at 1:01 AM Brian Hutchinson <b.hutchman@gmail.com>
> wrote:
> >
> > Hi,
> >
> > I'm using u-boot U-Boot 2019.04-4.19.35-1.1.0+g4d377539a1 in
> pre-programmed NOR flash and was using linux-fslc-imx 5.4.114 kernel and
> fw_printenv/fw_setenv were working fine.
> >
> > After upgrading to linux-fslc-imx 5.10.69, fw_setenv will not change any
> u-boot variable.  fw_printenv looks like it is working ok.  I've verified
> all my .config settings are the same with regard to MTD etc as my older
> 5.4.114 kernel.
> >
> > Any ideas what could be broken?
>
> Could it be that on 5.10 the MTD devices are registered in a different
> order, which causes a different mtd numbering of the devices?
>

Nope, cat /proc/mtd looks good.  Same order as in previous kernels.


> Does fw_setenv give any error?
>

It does not.  It shows no signs of a problem, returns no errors or warnings
at all.  It "looks" like it worked normal but does not change the u-boot
environment variable.

Regards,

Brian

[-- Attachment #2: Type: text/html, Size: 1797 bytes --]

  reply	other threads:[~2021-11-08 12:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08  4:01 fw_printenv works but fw_setenv does not after switching to linux-fslc-imx 5.10.69 from linux-fslc-imx 5.4.114 Brian Hutchinson
2021-11-08 10:49 ` [meta-freescale] " Fabio Estevam
2021-11-08 12:55   ` Brian Hutchinson [this message]
     [not found]     ` <5bf7fb5e-cdfd-81b0-cbbb-6b958b909fce@berginkonsult.se>
2021-11-09 14:06       ` Brian Hutchinson
     [not found]       ` <16B5E5E958FABAD3.3265@lists.yoctoproject.org>
2021-11-10 13:40         ` Brian Hutchinson
     [not found]   ` <16B59367D6CBF8AF.22718@lists.yoctoproject.org>
2021-11-08 19:02     ` Brian Hutchinson
     [not found] ` <a111ce56-fe57-a0f1-07d5-684acbbf61dc@berginkonsult.se>
2021-11-08 12:51   ` Brian Hutchinson
     [not found]     ` <73b9f65e-7938-7d99-d6c2-e93a74ecade3@berginkonsult.se>
2021-11-08 22:30       ` Brian Hutchinson

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=CAFZh4h-1famKHUGPxAr7fvT7mFu5rv7ecG-5TWj9nSa-Y+LFOA@mail.gmail.com \
    --to=b.hutchman@gmail.com \
    --cc=festevam@gmail.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.