From: Pascal Vizeli <pascal.vizeli@syshack.ch>
To: barebox@lists.infradead.org
Subject: Fwd: RaspberryPi 1/2(/3)
Date: Tue, 22 May 2018 15:29:13 +0200 [thread overview]
Message-ID: <CACvFaDdQXFGV6Qmqk3_H_UebDvzzc_+uEq=v5zyCk-mKL7Oktg@mail.gmail.com> (raw)
In-Reply-To: <CACvFaDfa+Od__ZcB=hcFBzJ3eqRv1ZAnwG4-EjVGHsaq3zmnEw@mail.gmail.com>
Hi Roland
Roland Hieber <r.hieber@pengutronix.de> schrieb am Di., 22. Mai 2018, 10:16:
>
>
> Which version of the RPi firmware are you using? I wrote that section
> while using the git tag 1.20171029, maybe they changed something
> again...
I use the latest one. I was not sure if the 20170129 is workable on a RPi3+
Anyway I try this version to release a beta, if they will work.
>
> What you can try to do is enable "low level debug messages" make
> menuconfig under "Debugging", and try to set the log level to something
> higher and see if you get any output. I think you also need to set
> "System Type" -> "Lowlevel debug UART" to the model you're using.
Perfect. I will debug it on new Firmware and maybe I can fix this and
make it runable on a RPi3+ too. They use same kind of CPU but need a
other DTS.
I'm happy if I can help on this amazing project.
Best regards
Pascal
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-05-22 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 15:51 Pascal Vizeli
2018-05-22 8:16 ` Roland Hieber
[not found] ` <CACvFaDfa+Od__ZcB=hcFBzJ3eqRv1ZAnwG4-EjVGHsaq3zmnEw@mail.gmail.com>
2018-05-22 13:29 ` Pascal Vizeli [this message]
2018-05-22 14:25 ` Pascal Vizeli
2018-05-22 17:38 ` Pascal Vizeli
2018-05-22 18:24 ` Oleksij Rempel
2018-05-22 19:50 ` Pascal Vizeli
2018-06-04 13:28 ` Roland Hieber
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='CACvFaDdQXFGV6Qmqk3_H_UebDvzzc_+uEq=v5zyCk-mKL7Oktg@mail.gmail.com' \
--to=pascal.vizeli@syshack.ch \
--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