From: Daniel Morandini <danielmorandini@me.com>
To: 9front@9front.org
Subject: Re: [9front] PXE booting Rpi
Date: Thu, 25 Mar 2021 11:55:42 +0100 [thread overview]
Message-ID: <0AD69C97-A018-4009-AA84-CC4A28FCCA78@me.com> (raw)
In-Reply-To: <1721CD21-19AF-482A-B75D-F56A903A57A1@me.com>
Hi people,
some updates (pi is still not getting my cmdline.txt args):
According to the UART logs, it looks like bootcode.bin is NOT
fetching the cmdline.txt file.
As soon as I do not know how and when this logs are emitted, I
double checked on the kernel side: In bcm, I added a “confdump”
function that dumps confname and confval values up to nconf as soon
as print is available, after the “bootargsinit” call in main.c:
empty.
I checked the Atag parsing code and it looks like we do not pass
the `if(parseatags(va, len) == 0 || parsedevtree(va, len) == 0`
line, hence no atag is parsed.
I compared miller’s bcm code and its logic seemed pretty similar
on this regard, I double checked by booting the rasp using his
kernel and indeed no configuration is parsed in that case too.
What I find wierd is that if I add the cmdline.txt file to
the sd card directly it is NOT read as well.
This is the contents of the file (xd -c cmdline.txt):
```
0000000 u s e r = d a n \n
0000009
```
Do you have any idea? I’m at the “what the fuck” point :D
Cheers,
dan
next prev parent reply other threads:[~2021-03-25 11:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 14:05 Daniel Morandini
2021-03-10 17:20 ` cinap_lenrek
2021-03-12 10:36 ` Daniel Morandini
2021-03-25 10:55 ` Daniel Morandini [this message]
2021-03-25 18:49 ` Noam Preil
2021-03-25 21:49 ` Noam Preil
2021-04-07 8:39 ` Daniel Morandini
2021-04-08 14:21 ` cinap_lenrek
2021-04-08 15:45 ` Daniel Morandini
2021-04-08 16:12 ` cinap_lenrek
2021-04-11 12:11 ` cinap_lenrek
2021-04-12 9:04 ` Daniel Morandini
2021-04-12 10:14 ` cinap_lenrek
2021-04-12 16:48 ` Daniel Morandini
2021-04-15 21:15 ` cinap_lenrek
2021-04-19 7:53 ` Daniel Morandini
2021-04-19 16:20 ` Daniel Morandini
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=0AD69C97-A018-4009-AA84-CC4A28FCCA78@me.com \
--to=danielmorandini@me.com \
--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).