From: Laszlo Ersek <lersek@redhat.com>
To: 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:10:37 +0200 [thread overview]
Message-ID: <e7b8d643-faad-1615-ac85-0d53e3288bf4@redhat.com> (raw)
In-Reply-To: <A070D88A736F404BA499D160F4A2EEBEB190DF0E@TOSBLRMBX02.TOSHIBA-TSIP.COM>
On 05/17/18 13:50, Tasniya Begum Kankudti wrote:
> Dear Sir/ Madam
>
> We are using OpenQ660 Board. we suspect that edk2 is the bootloader
> for the same. We are unable to find the ram initialization code in
> edk2 bootloader. Please help us to find the respective ram
> initialization code. Please do write back waiting for your reply.
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.
Laszlo
next prev parent reply other threads:[~2018-05-17 12:10 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 [this message]
2018-05-17 20:43 ` Rebecca Cran
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=e7b8d643-faad-1615-ac85-0d53e3288bf4@redhat.com \
--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