From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Udit Kumar <udit.kumar@nxp.com>
Cc: Pankaj Bansal <pankaj.bansal@nxp.com>,
Andrew Fish <afish@apple.com>,
"Olivier.Martin@arm.com" <Olivier.Martin@arm.com>,
Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Storing Non volatile variables on SD/NAND
Date: Fri, 27 Oct 2017 14:20:27 +0100 [thread overview]
Message-ID: <CAKv+Gu-8P4Oz2yt_0oAy2p3R=MynjGXjNWdJRz6ZQDiOjheFmA@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0402MB334169D2304E9D0B3D9892E2915A0@VI1PR0402MB3341.eurprd04.prod.outlook.com>
On 27 October 2017 at 10:37, Udit Kumar <udit.kumar@nxp.com> wrote:
> Thanks Ard.
>
>> The UEFI spec allows you to expose entry points into a DXE_RUNTIME_DRIVER
>> module via a UEFI configuration table, and the OS can use a driver that uses the
>> abstracted device rather than the real device. Performance is going to be
>
> Could you point me to some sample driver using this scheme,
> Mainly around OS implementation
>
I don't know of any examples, unfortunately. This is uncharted territory afaik.
next prev parent reply other threads:[~2017-10-27 13:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 13:52 Storing Non volatile variables on SD/NAND Udit Kumar
2017-09-18 15:43 ` Ard Biesheuvel
2017-09-18 16:52 ` Vladimir Olovyannikov
2017-09-19 5:28 ` Udit Kumar
2017-09-19 16:38 ` Ard Biesheuvel
2017-09-20 4:27 ` Udit Kumar
2017-09-20 4:47 ` Andrew Fish
2017-09-20 5:09 ` Udit Kumar
2017-09-20 5:17 ` Andrew Fish
2017-09-20 14:51 ` Pankaj Bansal
2017-09-20 17:34 ` Udit Kumar
2017-09-20 17:39 ` Ard Biesheuvel
2017-09-20 17:39 ` Ard Biesheuvel
2017-09-20 17:46 ` Andrew Fish
2017-10-27 9:35 ` Udit Kumar
2017-10-27 9:37 ` Udit Kumar
2017-10-27 13:20 ` Ard Biesheuvel [this message]
2017-10-27 17:46 ` Jeremy Linton
2017-10-28 3:09 ` Udit Kumar
2017-10-30 23:10 ` Jeremy Linton
2017-10-31 4:25 ` Udit Kumar
2017-09-20 17:34 ` Andrew Fish
2017-09-18 20:47 ` Jeremy Linton
2017-09-18 20:53 ` Ard Biesheuvel
2017-09-19 5:27 ` Udit Kumar
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='CAKv+Gu-8P4Oz2yt_0oAy2p3R=MynjGXjNWdJRz6ZQDiOjheFmA@mail.gmail.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