Hello again,
just after sending the last message I continued testing, and went have
a look at the various CONFIG options I used, especially their help text...
The problem was PEBKAC, I RTFM'ed myself with:
CONFIG_SYS_MMC_ENV_PART:
MMC hardware partition device number on the platform where the
e
Hello Simon,
On Thu, Sep 12, 2024 at 1:02 AM Simon Glass wrote:
> Looking at env_erase()
> It calls drv->erase() which for mmc is:
> .erase = ENV_ERASE_PTR(env_mmc_erase)
>
> I see this:
>
> if (IS_ENABLED(CONFIG_SYS_REDUNDAND_ENVIRONMENT)) {
>copy = 1;
>
>if (IS_ENABLED(ENV_MMC_HWPART_RE
Hi Vincent,
On Sun, 8 Sept 2024 at 22:38, Vincent Legoll wrote:
>
> Hello,
>
> I'm struggling to setup u-boot to be able to save the environment.
>
> The board is Pine64 QuartzPro64.
>
> ATF is collabora's:
> https://gitlab.collabora.com/hardware-enablement/rockchip-3588/trusted-firmware-a.git
>
Hello,
I'm struggling to setup u-boot to be able to save the environment.
The board is Pine64 QuartzPro64.
ATF is collabora's:
https://gitlab.collabora.com/hardware-enablement/rockchip-3588/trusted-firmware-a.git
collabora-enablement-tfa/master
44418fce30938ee483fbfc79cc32fde33753d1aa
rkbin is
> From: Ian Ray
> Disable the unused persistent environment.
> Signed-off-by: Ian Ray
> Signed-off-by: Sebastian Reichel
Applied to u-boot-imx, master, thanks !
Best regards,
Stefano Babic
--
=
DENX Software Engi
From: Ian Ray
Disable the unused persistent environment.
Signed-off-by: Ian Ray
Signed-off-by: Sebastian Reichel
---
configs/ge_bx50v3_defconfig | 2 +-
configs/mx53ppd_defconfig | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/configs/ge_bx50v3_defconfig b/configs
2018 at 06:04:05PM +0530, Sumit Garg wrote:
> > > > On Mon, 26 Nov 2018 at 16:51, Sumit Garg
> > > > wrote:
> > > > >
> > > > > Currently on qemu-arm platforms environment is kept in RAM.
> > > > > Instead use pflash device
16:51, Sumit Garg
> > > wrote:
> > > >
> > > > Currently on qemu-arm platforms environment is kept in RAM.
> > > > Instead use pflash device 1 to provide persistent environment
> > > > support across device reset.
> > > >
> > > >
On Thu, Dec 13, 2018 at 02:43:58AM +0200, Tuomas Tynkkynen wrote:
> > Another use case is atf + u-boot (although I don't know people are
> > interested in it). Put bl1.bin in flash0(0x0-0x400) and put
> > fip.bin in flash1(0x400-0x800). Please note that, with
> > secure=on, flash0 is in
On Mon, Nov 26, 2018 at 04:50:17PM +0530, Sumit Garg wrote:
> Currently on qemu-arm platforms environment is kept in RAM. Instead
> use pflash device 1 to provide persistent environment support across
> device reset.
>
> Also (optionally) provide support for persistent environmen
in RAM.
> > > Instead use pflash device 1 to provide persistent environment
> > > support across device reset.
> > >
> > > Also (optionally) provide support for persistent environment
> > > across qemu machine OFF/ON using following instructions:
>
t; > > On Mon, 26 Nov 2018 at 16:51, Sumit Garg wrote:
> > > > >
> > > > > Currently on qemu-arm platforms environment is kept in RAM. Instead
> > > > > use pflash device 1 to provide persistent environment support across
> > > >
> > > > Currently on qemu-arm platforms environment is kept in RAM. Instead
> > > > use pflash device 1 to provide persistent environment support across
> > > > device reset.
> > > >
> > > > Also (optionally) provide support for persistent en
e pflash device 1 to provide persistent environment support across
> > > device reset.
> > >
> > > Also (optionally) provide support for persistent environment across
> > > qemu machine OFF/ON using following instructions:
> > >
> > > - Create
On Tue, Dec 11, 2018 at 06:04:05PM +0530, Sumit Garg wrote:
> On Mon, 26 Nov 2018 at 16:51, Sumit Garg wrote:
> >
> > Currently on qemu-arm platforms environment is kept in RAM. Instead
> > use pflash device 1 to provide persistent environment support across
> >
On Mon, 26 Nov 2018 at 16:51, Sumit Garg wrote:
>
> Currently on qemu-arm platforms environment is kept in RAM. Instead
> use pflash device 1 to provide persistent environment support across
> device reset.
>
> Also (optionally) provide support for persistent environment across
# I have a similar patch in my local branch :)
> > >
> >
> > IIRC, we did sync on this work.
> >
> > > On Mon, Nov 26, 2018 at 04:50:17PM +0530, Sumit Garg wrote:
> > > > Currently on qemu-arm platforms environment is kept in RAM. Instead
>
>
> > On Mon, Nov 26, 2018 at 04:50:17PM +0530, Sumit Garg wrote:
> > > Currently on qemu-arm platforms environment is kept in RAM. Instead
> > > use pflash device 1 to provide persistent environment support across
> > > device reset.
> > >
> > &g
is kept in RAM. Instead
> > use pflash device 1 to provide persistent environment support across
> > device reset.
> >
> > Also (optionally) provide support for persistent environment across
> > qemu machine OFF/ON using following instructions:
> >
> > -
Sumit,
# I have a similar patch in my local branch :)
On Mon, Nov 26, 2018 at 04:50:17PM +0530, Sumit Garg wrote:
> Currently on qemu-arm platforms environment is kept in RAM. Instead
> use pflash device 1 to provide persistent environment support across
> device reset.
>
> A
Currently on qemu-arm platforms environment is kept in RAM. Instead
use pflash device 1 to provide persistent environment support across
device reset.
Also (optionally) provide support for persistent environment across
qemu machine OFF/ON using following instructions:
- Create envstore.img using
ing to automate some tests and one of the parts of the
>>> project requires the use of persistent environment.
>>>
>>> Due performance advantages we would like to use x86 with KVM to
>>> execute the tests however after booting QEMU with the UEFI payload it
>>> turn
On Thu, Dec 8, 2016 at 4:55 PM, Simon Glass wrote:
> Hi Otavio,
>
> On 8 December 2016 at 10:39, Otavio Salvador
> wrote:
>> Hello everyone,
>>
>> We are trying to automate some tests and one of the parts of the
>> project requires the use of persisten
Hi Otavio,
On 8 December 2016 at 10:39, Otavio Salvador
wrote:
> Hello everyone,
>
> We are trying to automate some tests and one of the parts of the
> project requires the use of persistent environment.
>
> Due performance advantages we would like to use x86 with KVM to
&
Hello everyone,
We are trying to automate some tests and one of the parts of the
project requires the use of persistent environment.
Due performance advantages we would like to use x86 with KVM to
execute the tests however after booting QEMU with the UEFI payload it
turns out the environment
25 matches
Mail list logo
