From: Matthias Fuchs <matthias.fuchs@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH/RFC] mx28: print bootmode with cpuinfo
Date: Tue, 24 Jan 2012 15:10:13 +0100 [thread overview]
Message-ID: <4F1EBBC5.9030408@esd.eu> (raw)
In-Reply-To: <CAOMZO5Dy29sym0BbPQwDqs=G50AOgupZsqb9-QRf+NxYb0A18g@mail.gmail.com>
On 23.01.2012 21:33, Fabio Estevam wrote:
> Hi Matthias,
>
> On 1/18/12, Matthias Fuchs <matthias.fuchs@esd.eu> wrote:
>> Hi,
>>
>> while playing around with the mx28evk and differnet bootmedia
>> I found it helpful to see the current bootmode without
>> running to the board and checking it's switches. Also
>> some other CPU (e.g. 440 PowerPCs) print some kind of bootstrap
>> configuration during startup.
>>
>> The patch probably needs some little cleanup. But the main issue might
>> be the way how it passes the information from SPL to 2nd stage.
>> I am note sure if those scratch registers are somehow holy :-)
>
> I tested your patch and it worked fine.
>
> What I really liked about it is that it fixed a real issue that I was seeing:
> after booting the kernel and issuing a "reboot"command, kernel did
> shutdown, reset the system, but then U-boot got stuck showing "DRAM: 0
> bytes".
Hmm ...
>
> So maybe you could split this patch in two parts:
>
> - One patch that touches the HW_DIGCTRL_SCRATCH register (this part is
> what fixed the RAM size retrievel after a "reboot" in the kernel
And what is this part? I was not aware of this issue. What exactly part
of my patch fixes this issue?
And finally I am not sure if we should use the scratch registers for
passing the boot mode at all.
Matthias
next prev parent reply other threads:[~2012-01-24 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 11:41 [U-Boot] [PATCH/RFC] mx28: print bootmode with cpuinfo Matthias Fuchs
2012-01-23 20:33 ` Fabio Estevam
2012-01-24 14:10 ` Matthias Fuchs [this message]
2012-01-24 15:12 ` Fabio Estevam
-- strict thread matches above, loose matches on Subject: below --
2012-01-18 11:41 Matthias Fuchs
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=4F1EBBC5.9030408@esd.eu \
--to=matthias.fuchs@esd.eu \
--cc=u-boot@lists.denx.de \
/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