From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <lersek@redhat.com>
Received-SPF: Pass (sender SPF authorized) identity=mailfrom;
 client-ip=66.187.233.73; helo=mx1.redhat.com; envelope-from=lersek@redhat.com;
 receiver=edk2-devel@lists.01.org 
Received: from mx1.redhat.com (mx3-rdu2.redhat.com [66.187.233.73])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by ml01.01.org (Postfix) with ESMTPS id 7C8D7203B990B
 for <edk2-devel@lists.01.org>; Thu, 17 May 2018 05:10:40 -0700 (PDT)
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com
 [10.11.54.4])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.redhat.com (Postfix) with ESMTPS id EF2228082559;
 Thu, 17 May 2018 12:10:39 +0000 (UTC)
Received: from lacos-laptop-7.usersys.redhat.com (ovpn-120-28.rdu2.redhat.com
 [10.10.120.28])
 by smtp.corp.redhat.com (Postfix) with ESMTP id ED8922026DEF;
 Thu, 17 May 2018 12:10:38 +0000 (UTC)
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>
References: <A070D88A736F404BA499D160F4A2EEBEB190DF0E@TOSBLRMBX02.TOSHIBA-TSIP.COM>
From: Laszlo Ersek <lersek@redhat.com>
Message-ID: <e7b8d643-faad-1615-ac85-0d53e3288bf4@redhat.com>
Date: Thu, 17 May 2018 14:10:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <A070D88A736F404BA499D160F4A2EEBEB190DF0E@TOSBLRMBX02.TOSHIBA-TSIP.COM>
X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16
 (mx1.redhat.com [10.11.55.8]); Thu, 17 May 2018 12:10:40 +0000 (UTC)
X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.11.55.8]);
 Thu, 17 May 2018 12:10:40 +0000 (UTC) for IP:'10.11.54.4'
 DOMAIN:'int-mx04.intmail.prod.int.rdu2.redhat.com'
 HELO:'smtp.corp.redhat.com' FROM:'lersek@redhat.com' RCPT:''
Subject: Re: Ram initialization sequence in edk2
X-BeenThere: edk2-devel@lists.01.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: EDK II Development  <edk2-devel.lists.01.org>
List-Unsubscribe: <https://lists.01.org/mailman/options/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=unsubscribe>
List-Archive: <http://lists.01.org/pipermail/edk2-devel/>
List-Post: <mailto:edk2-devel@lists.01.org>
List-Help: <mailto:edk2-devel-request@lists.01.org?subject=help>
List-Subscribe: <https://lists.01.org/mailman/listinfo/edk2-devel>,
 <mailto:edk2-devel-request@lists.01.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 12:10:41 -0000
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit

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