From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rpi4B (4GB) model
Date: Sat, 18 Apr 2020 18:52:06 +0200 [thread overview]
Message-ID: <65186E9182C9F9C9907872FD3F6CDDFC@felloff.net> (raw)
In-Reply-To: <413783E322C29B59A714F9093FC3E933@hera.eonet.ne.jp>
> What I did bad?
It is possible that the firmware changed the format of the
device tree?
The kernel uses device tree to determine the memory size and
adds a *memsize=<topaddr1> <base2> <topaddr2> ... parameter
to the boot configuration.
you can try to read it with if it is there:
cat '#ec/*memsize'
if that file is missing, it could be that the device tree is
not passed to the kernel or the field format has changed somehow
with the new firmware.
the relevant code is in bcm/bootargc.c where devtreeprop() gets
called for every device tree property and we filter out the
/memory/reg property and add a *maxmem boot parameter when
it does not already exist.
debugging is a bit tricky in that code because we havnt setup
the framebuffer or serial console yet.
i only got a raspi4 with 2gb. but i can still try to see if it
can be reproduced here with the latest firmware. if i can find
the time...
--
cinap
next prev parent reply other threads:[~2020-04-18 16:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 5:30 kokamoto
2020-04-18 16:52 ` cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-21 22:31 kokamoto
2020-04-22 17:52 ` cinap_lenrek
2020-04-30 6:20 ` kokamoto
2020-04-30 6:21 ` kokamoto
2020-04-30 7:54 ` hiro
2020-04-30 9:41 ` kokamoto
2020-04-30 10:21 ` hiro
2020-04-20 6:47 kokamoto
2020-04-20 1:31 kokamoto
2020-04-21 9:06 ` cinap_lenrek
2020-04-14 8:19 kokamoto
2020-04-14 5:20 kokamoto
2020-04-18 17:01 ` [9front] " cinap_lenrek
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=65186E9182C9F9C9907872FD3F6CDDFC@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).