From: Tasniya Begum Kankudti <Tasniya.Kankudti@toshiba-tsip.com>
To: "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: Ram initialization sequence in edk2
Date: Thu, 17 May 2018 11:50:11 +0000 [thread overview]
Message-ID: <A070D88A736F404BA499D160F4A2EEBEB190DF0E@TOSBLRMBX02.TOSHIBA-TSIP.COM> (raw)
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.
Thanks and Regards
Tasniya
The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.
Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.
next reply other threads:[~2018-05-17 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 11:50 Tasniya Begum Kankudti [this message]
2018-05-17 12:10 ` Ram initialization sequence in edk2 Laszlo Ersek
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=A070D88A736F404BA499D160F4A2EEBEB190DF0E@TOSBLRMBX02.TOSHIBA-TSIP.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