From: Sascha Hauer <s.hauer@pengutronix.de>
To: andreas.willig@rafi.de
Cc: barebox@lists.infradead.org
Subject: Re: Antwort: Re: i.MX6Q Boot from NAND
Date: Thu, 27 Feb 2014 08:30:26 +0100 [thread overview]
Message-ID: <20140227073026.GC17250@pengutronix.de> (raw)
In-Reply-To: <OF16C06084.7F23E3FD-ONC1257C8B.0027623B-C1257C8B.0027D344@o0802.rafi.inhouse>
On Wed, Feb 26, 2014 at 08:15:00AM +0100, andreas.willig@rafi.de wrote:
> Hi Sascha
> i saw this Thread too in the archives, but since no code was entered into
> repo i suppose the effort was not successful. By my opinion it should be
> solvable, since U-Boot get's it running and sources are not that different
> concerning this point. I did compare the BCB section in U-Boot with BCB
> sections in Barebox and for the first point of view, i did not find the
> difference, I'm just about to debug this using Lauterbach.
>
> Btw is there a well known procedure to keep i.MX6Q cool? I got a passive
> cooler, but especially during debugging system get's heat up over 80�C !!!
> Which issues a reset using u-boot.
Philipp has recently sent a patch which turns off the GPU clocks in
barebox. This could help a little. The path sits in -next right now.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-02-27 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 6:30 andreas.willig
2014-02-26 7:06 ` Sascha Hauer
[not found] ` <OF16C06084.7F23E3FD-ONC1257C8B.0027623B-C1257C8B.0027D344@o0802.rafi.inhouse>
2014-02-27 7:30 ` Sascha Hauer [this message]
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=20140227073026.GC17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=andreas.willig@rafi.de \
--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