From: Konstantin Kletschke <konstantin.kletschke@inside-m2m.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Howto implement bootchooser <-> rauc interaction
Date: Fri, 17 Dec 2021 13:43:48 +0100 [thread overview]
Message-ID: <YbyGBHs1YWVcgE5X@Hephaistos> (raw)
In-Reply-To: <ef8a2a82-91f5-5401-a564-a0ab20da4772@pengutronix.de>
Hi :-)
On Fri, Dec 17, 2021 at 10:46:42AM +0100, Ahmad Fatoum wrote:
> It was backported to stable in v5.10.20. Backport commit is 663a18271.
Sorry my git/google-foo is unsufficient, how do I get my hands on this
commit?
> > So one has to take care of the parent note size being big enough to contain the sum of
> > all length and thse itself must not overlap, right?
>
> Yes. Device Tree compiler helps here a bit by warning if two nodes on the same bus
> have the same base address.
Okay.
> Open Firmware. It's the original standard that described device trees.
Oh, I wasn't aware, thanks for the information.
> > On the other hand, I could access plenty of space unallocated after the MBR if 1st partition
> > starts at a late sector like 1024 or so.
>
> Latter is what I usually do.
Okay.
> arch/arm/dts/imx6qdl-prti6q-emmc.dtsi places it on eMMC. Check it out.
Yes, I will do, thank you!
> > And is doing this state thing in a file (for example on the 1st FAT where barebox.env is)
> > for barebox and raux/barebox-state possible or not?
>
> FAT isn't power-fail safe. It's ok for reading or writing stuff during
> development (e.g. environment), but you really don't want to use it
> for barebox-state that's meant to be power-fail safe.
Okay again, I am convinced about the no-file-in-FAT state.
So, just to be shure for the state OF partition placed after the MBR before 1st
MBR partition:
If I have 1st partition's start sector being 2048 I hafe plenty of room
before this after the MBR.
The barebox state OF partition should be in there and I could place it
at
reg = <0x300 0xfffff>
because the MBR ends at 0x1ff and the 1st partition starts at
sector 2048 ( 2048*512byte=1MB=0x10000), is that correct, is the reg
addressing done this way?
Of course a length of 0xfffff is far too much,
just to get a picture. Also to transfer this to an OF partition in a MBR
partition.
The container partition reg = <0xc0000 0x40000> in imx6qdl-prti6q-emmc.dtsi seems
to be directly going to below a MBR partiton starting at 2048th sector
with size 256kB, correct?
Thanks for your patience!
Regards
Konstantin
INSIDE M2M GmbH
Konstantin Kletschke
Berenbosteler Straße 76 B
30823 Garbsen
Telefon: +49 (0) 5137 90950136
Mobil: +49 (0) 151 15256238
Fax: +49 (0) 5137 9095010
konstantin.kletschke@inside-m2m.de
http://www.inside-m2m.de
Geschäftsführung: Michael Emmert, Ingo Haase, Dr. Fred Könemann, Derek Uhlig
HRB: 111204, AG Hannover
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-12-17 12:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 12:40 Konstantin Kletschke
2021-12-03 17:52 ` Trent Piepho
2021-12-05 22:55 ` Roland Hieber
2021-12-06 8:52 ` Konstantin Kletschke
2021-12-14 21:40 ` Konstantin Kletschke
2021-12-15 10:56 ` Ahmad Fatoum
2021-12-16 19:35 ` Konstantin Kletschke
2021-12-17 10:00 ` Ahmad Fatoum
2021-12-17 12:50 ` Konstantin Kletschke
2022-01-03 15:24 ` Roland Hieber
2021-12-06 8:30 ` Konstantin Kletschke
2021-12-14 21:28 ` Konstantin Kletschke
2021-12-15 10:50 ` Ahmad Fatoum
[not found] ` <297b3425baa118783dccb6446900fbfa@inside-m2m.de>
2021-12-16 19:42 ` Fwd: " Konstantin Kletschke
2021-12-17 9:46 ` Ahmad Fatoum
2021-12-17 12:43 ` Konstantin Kletschke [this message]
2021-12-17 13:08 ` Ahmad Fatoum
2021-12-17 14:21 ` Konstantin Kletschke
2021-12-22 14:05 ` Konstantin Kletschke
2022-01-05 17:50 ` Ahmad Fatoum
2022-01-06 9:59 ` Konstantin Kletschke
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=YbyGBHs1YWVcgE5X@Hephaistos \
--to=konstantin.kletschke@inside-m2m.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox