9front - general discussion about 9front
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] rpi4B (4GB) model
Date: Tue, 21 Apr 2020 11:06:24 +0200	[thread overview]
Message-ID: <00AA13705B1610D95B45D50EB2B40217@felloff.net> (raw)
In-Reply-To: <6AB574B0E601E9EA10AA6E5753096459@hera.eonet.ne.jp>

> I cannot find '#ec/*memsize', found only
> 8250.nr_uarts, bcm2708_fb.fbdepth, bcm2708_fb.fbheight, bcm2708_fb_fbswap, bcm2708_fb_fbwidth
> cma, coherent_pool, console, smsc95xx.macaddr, vc_mem.mem_base, vc_mem.mem_size.

ok,

this means we couldnt detect the memory size from device tree.

looks like they changed the device tree names arround:

https://github.com/raspberrypi/linux/commit/4b17654f51fd87c42cda3217b0863e6aa1df49b9#diff-ac03c9402b807c11d42edc9e8d03dfc7

you can try the following patch?

diff -r f9f922fd127d sys/src/9/bcm/bootargs.c
--- a/sys/src/9/bcm/bootargs.c	Mon Apr 20 00:08:35 2020 +0200
+++ b/sys/src/9/bcm/bootargs.c	Tue Apr 21 10:59:21 2020 +0200
@@ -89,7 +89,8 @@
 static void
 devtreeprop(char *path, char *key, void *val, int len)
 {
-	if(strcmp(path, "/memory") == 0 && strcmp(key, "reg") == 0){
+	if((strcmp(path, "/memory") == 0 || strcmp(path, "/memory@0") == 0)
+	&& strcmp(key, "reg") == 0){
 		if(findconf("*maxmem") < 0 && len > 0 && (len % (3*4)) == 0){
 			uvlong top;
 			uchar *p = val;


  reply	other threads:[~2020-04-21  9:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20  1:31 kokamoto
2020-04-21  9:06 ` 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-16  5:30 kokamoto
2020-04-18 16:52 ` 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=00AA13705B1610D95B45D50EB2B40217@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).