From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fuchs Date: Tue, 24 Jan 2012 15:10:13 +0100 Subject: [U-Boot] [PATCH/RFC] mx28: print bootmode with cpuinfo In-Reply-To: References: <4F16AFE2.7010200@esd.eu> Message-ID: <4F1EBBC5.9030408@esd.eu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 23.01.2012 21:33, Fabio Estevam wrote: > Hi Matthias, > > On 1/18/12, Matthias Fuchs 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