From: Pete Batard <pete@akeo.ie>
To: Marcin Wojtas <mw@semihalf.com>,
Michael Zimmermann <sigmaepsilon92@gmail.com>
Cc: Rebecca Cran <rebecca@bluestop.org>,
edk2-devel-01 <edk2-devel@lists.01.org>
Subject: Re: EXT FS support
Date: Tue, 22 Nov 2016 18:25:03 +0000 [thread overview]
Message-ID: <c4049fa6-16d2-a73b-ab04-7c770bf86aca@akeo.ie> (raw)
In-Reply-To: <CAPv3WKfb29xHS2j1akMrPH4u6yevhfW7nNDqKXXRBWHgvhC_ng@mail.gmail.com>
On 2016.11.22 17:16, Marcin Wojtas wrote:
> There's no GRUB, platform simply boots to the Shell.
I think there may be some confusion.
All the drivers we linked you to are pure UEFI drivers. It doesn't
matter if they were a port from GRUB or something else, the code was
converted to work as a standalone UEFI driver. Especially you don't need
to have GRUB running or anything. You can just use the "load" command in
the shell to load the driver, and then access the file system.
I believe you should be able to download any of the ext binary drivers
mentioned and use them in your shell right away to access your file
system from it.
> I'd be grateful also for pointing the easiest way to port one of the
> EXT solutions. I went over all url's provided and I must say porting
> seems not trivial.
I don't think there's anything to port. The drivers have already been
ported for UEFI (though, in the case of efifs, they rely on gnu-efi for
compilation rather than EDK2 - but this has the benefit of being able to
use a regular Visual Studio 2015 solution).
Regards,
/Pete
next prev parent reply other threads:[~2016-11-22 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 15:25 EXT FS support Marcin Wojtas
2016-11-22 16:19 ` Pete Batard
2016-11-22 16:41 ` Rebecca Cran
2016-11-22 16:59 ` Michael Zimmermann
2016-11-22 17:16 ` Marcin Wojtas
2016-11-22 18:25 ` Pete Batard [this message]
2016-11-22 21:31 ` Rod Smith
2016-11-23 19:50 ` Laszlo Ersek
2016-11-23 20:01 ` Michael Zimmermann
2016-11-23 20:11 ` Laszlo Ersek
2016-11-24 1:03 ` Rebecca Cran
2016-11-24 8:27 ` Laszlo Ersek
2016-11-28 21:15 ` Carsey, Jaben
2016-11-22 18:18 ` Pete Batard
2016-11-22 16:40 ` 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=c4049fa6-16d2-a73b-ab04-7c770bf86aca@akeo.ie \
--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