public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Rebecca Cran <rebecca@bluestop.org>
To: Laszlo Ersek <lersek@redhat.com>,
	Tasniya Begum Kankudti <Tasniya.Kankudti@toshiba-tsip.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "ArunKumar JTS." <arunkumar.sekarbabu@TOSHIBA-TSIP.COM>,
	"Amith B. V" <Amith.Venkataramana@toshiba-tsip.com>,
	Vadivelan M <Vadivelan.Mani@toshiba-tsip.com>
Subject: Re: Ram initialization sequence in edk2
Date: Thu, 17 May 2018 14:43:14 -0600	[thread overview]
Message-ID: <5ea7fb31-fe42-17ea-0512-efa51b36881c@bluestop.org> (raw)
In-Reply-To: <e7b8d643-faad-1615-ac85-0d53e3288bf4@redhat.com>

On 05/17/2018 06:10 AM, Laszlo Ersek wrote:
>
> The memory controller (or other silicon) initialization code is usually
> one of the most proprietary parts of any platform firmware. It's pretty
> unlikely you can get the source for it from anyone else than the
> platform manufacturer, and that's assuming they're willing to let you
> see it at all, even for $$$ and under strict NDA.

Agreed. Just to add that you can see a real-world example of memory 
controller initialization code - for the Quark (used in the discontinued 
Intel Galileo development boards) at 
https://github.com/tianocore/edk2/tree/master/QuarkSocPkg/QuarkNorthCluster/MemoryInit/Pei 
.

-- 
Rebecca


      reply	other threads:[~2018-05-17 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 11:50 Ram initialization sequence in edk2 Tasniya Begum Kankudti
2018-05-17 12:10 ` Laszlo Ersek
2018-05-17 20:43   ` Rebecca Cran [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-list 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=5ea7fb31-fe42-17ea-0512-efa51b36881c@bluestop.org \
    --to=devel@edk2.groups.io \
    /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