From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] raspberry pi 4 arm64 test image
Date: Wed, 21 Aug 2019 23:35:11 +0200 [thread overview]
Message-ID: <BDD56FDDF8E5267BCEE9B3F9226DFA17@felloff.net> (raw)
In-Reply-To: 20190821192049.E93D41570CE9@mail.bitblocks.com
ok, i prepared a kernel with debug prints. (i basically
buffer the debug outputs in kmesg and dump them on the
serial console and screen once they get initialized).
http://felloff.net/usr/cinap_lenrek/9pi4
i suspect that the device tree /memory/reg property
might not be a single 12 byte entry. and thats why
theres no *maxmem variable in #ec.
i also added some prints to fbinit() just to make
sure...
on my pi4, i get:
/memory/reg[12]: 00000000000000003E600000
confinit: *maxmem=0x3e600000
confinit: memsize=0x3e600000
confinit: getramsize() => 00000000 00000000
confinit: mem[0] => 00000000 3e600000
127 holes free
0x00670000 0x19310000 415891456
415891456 bytes free
fbinit: 1280x1024x16
fbinit: base=fed7b000
fbinit: va=ffffffff1ed7b000
Plan 9
...
--
cinap
next reply other threads:[~2019-08-21 21:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 21:35 cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-08-23 20:15 cinap_lenrek
2019-08-21 23:58 cinap_lenrek
2019-08-22 4:37 ` Bakul Shah
2019-08-21 22:24 cinap_lenrek
2019-08-21 21:59 cinap_lenrek
2019-08-21 22:18 ` Bakul Shah
2019-08-22 7:07 ` Richard Miller
2019-08-22 8:58 ` Steve Simon
2019-08-22 20:26 ` Charles Forsyth
2019-08-21 19:53 cinap_lenrek
2019-08-21 20:02 ` Richard Miller
2019-08-21 22:20 ` Bakul Shah
2019-08-21 17:56 cinap_lenrek
2019-08-21 19:20 ` Bakul Shah
2019-08-21 19:25 ` Richard Miller
2019-08-21 20:05 ` Richard Miller
2019-08-21 20:27 ` Bakul Shah
2019-08-21 19:57 ` Richard Miller
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=BDD56FDDF8E5267BCEE9B3F9226DFA17@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/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).