public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] M28: Added guarding for reserved bits in GPIO driver
Date: Tue, 22 Nov 2011 19:08:55 +0100	[thread overview]
Message-ID: <201111221908.55366.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAFF982B-DC36-4B39-B5C0-E121BFC8B57E@delien.nl>

> > To make things simple for users, there's standard layout. It's actually
> > at sector 2048 btw.
> 
> Got that.
> 
> > That's what happens internally, it's just that some pieces (like sector
> > offset of the partition!) need to be filled into the bootstream header
> > by the mxsboot utility -- see mxsboot -h for how to change that.
> 
> You're completely right! This sector needs to be know build-time because it
> is specified in the Boot Stream Block of the Boot Stream header. I forgot
> about that, because I hid that in a script some time ago. That script was
> basically a rewritten version of the broken one that was supplied with the
> SDK.
> 
> Come to think of it, it's a bit weird that the sector the BSB is located
> in, is specified in the BSB: When reading it, it already knows this
> sector, because that's the sector it is reading from at that moment...
> 
> > The 2048 sector offset was chosen because that's standard in Linux now
> > for first partiiton.
> 
> Agreed.
> 
> > What do you mean?
> 
> What I meant to ask was how you solved the paradoxic problem that U-Boot
> needs to initialize SD-RAM before it can be loaded (and obviously U-Boot
> needs to be loaded before it can initialize SD-RAM).

Well we have U-Boot SPL, which is loaded into SRAM, inits DRAM, pinmux etc., 
then we pass execution back to BootROM to load U-Boot into DRAM and execute it.

> 
> Freescale solved this problem by putting multiple bootlets in their
> bootstream. The first one is small enough to fit SRAM and it enables the
> PMIC's LDOs to power up all power domains. The second one too is small
> enough to fit SRAM. Loading it overwrites the first one and running it
> initializes SD-RAM. The third one is either U-Boot or a Kernel and is
> directly loaded into the now initialized SD-RAM.

Yea, you can load kernel directly via U-Boot SPL too.
> 
> I figured that your solution links U-Boot in a clever way that the lower
> part fitting SRAM will initialize the PMIC and SD-RAM, after which U-Boot
> will load the remainder of itself from MMC into SD-RAM.

See above.
> 
> > You can adjust that, see above.
> 
> Understood.
> 
> Cheers,
> 
>         Robert.

  reply	other threads:[~2011-11-22 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 14:41 [U-Boot] [PATCH] M28: Added guarding for reserved bits in GPIO driver Robert Deliën
2011-11-22 14:49 ` Marek Vasut
     [not found]   ` <B4232BD0-3457-4DC5-9A4A-4E16719BA157@delien.nl>
2011-11-22 15:25     ` Marek Vasut
2011-11-22 16:48       ` Robert Deliën
2011-11-22 18:08         ` Marek Vasut [this message]
2011-11-22 18:20 ` Marek Vasut
2011-11-22 19:24   ` Robert Deliën
2011-11-22 22:36     ` Marek Vasut
2011-11-23 10:47   ` Robert Deliën
2011-11-23 10:59     ` Marek Vasut
2011-11-23 12:36       ` Robert Deliën
2011-11-22 21:09 ` Mike Frysinger
2011-11-22 21:16   ` Robert Deliën

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=201111221908.55366.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.com \
    --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