hi:
everybody! i'am porting edkii to a arm cortex a7 soc, everything looks well.
but when i enter shell,
there is a problem: i can‘t use "ctrl+c" to stop app in my uart console. that
means ctrl+c do not work on my platform !
is there any guys had meet such a situation ?
zhengjiewen2005
From: edk2-devel-request
Date: 2013-10-17 20:55
To: edk2-devel
Subject: edk2-devel Digest, Vol 46, Issue 34
Send edk2-devel mailing list submissions to
edk2-devel@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/edk2-devel
or, via email, send a message with subject or body 'help' to
edk2-devel-requ...@lists.sourceforge.net
You can reach the person managing the list at
edk2-devel-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of edk2-devel digest..."
Today's Topics:
1. Re: NTFS partition driver and partition imaging (Rod Smith)
2. Re: NTFS partition driver and partition imaging (Blibbet)
3. Re: NTFS partition driver and partition imaging (Rod Smith)
4. problem in openprotocol (parmeshwr_pra...@dell.com)
----------------------------------------------------------------------
Message: 1
Date: Wed, 16 Oct 2013 12:45:22 -0400
From: Rod Smith <rodsm...@rodsbooks.com>
Subject: Re: [edk2] NTFS partition driver and partition imaging
To: edk2-devel@lists.sourceforge.net
Message-ID: <525ec2a2.6040...@rodsbooks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 10/15/2013 09:23 PM, Blibbet wrote:
>
> It seems silly to require that FAT lives on forever with UEFI, when
> there are more native (and sometimes more secure) solutions for each OS.
> Especialy given UEFI has a file system driver model.
Although some hardware is designed with a single OS in mind, many
computers are OS-agnostic. If you buy a motherboard from MSI, ASUS, or
whoever, or even if you buy a computer from Dell, HP, Apple, or whoever,
you can load Windows, Linux, FreeBSD, or other OSes on it. Ripping out
the EFI FAT driver and replacing it with a driver for NTFS, ext4fs, or
some other OS-specific filesystem would just make it harder to use the
computer with anything but the OS for which that filesystem was
designed. Note that Apple's HFS+ EFI driver supplements, but does not
replace, the FAT driver. If Apple had replaced the FAT driver with an
HFS+ driver, it would have just made it harder to install other EFI-mode
OSes on their hardware.
FAT may be klunky, but it's the closest thing we've got to a cross-OS
filesystem. Every major OS has FAT drivers, and can therefore be used to
maintain an ESP. The ESP needn't be a big partition, and the benefit of
advanced filesystem features on the ESP is limited at best, so FAT has
the benefit of working and creating a minimal number of follow-on problems.
> It would be nice if EDK included CD and DVD media file systems, at least
> binaries like the FAT driver.
There is an open source ISO-9660 driver for EFI, but it's licensed under
the GPL. It began life as part of Christoph Pfisterer's rEFIt project
(http://refit.sourceforge.net), but it wasn't really completed as part
of that project. Oracle took it up and released a finished version as
part of VirtualBox (https://www.virtualbox.org). I also distribute a
slightly modified version of this driver with rEFInd
(http://www.rodsbooks.com/refind/).
Because it's GPLed, the Oracle ISO-9660 driver can't be folded back into
the EDK 2. (It was GPLed by Oracle before I touched it, so there's
nothing I can do about that.) That said, Pfisterer wrote a bunch of
common support files that are now used by about half a dozen drivers
(including the ISO-9660 driver), and Pfisterer's original versions of
these files, as well as his original fsw_iso9660.c file, all use the BSD
license. If you wanted to use these rEFIt files as a starting point for
an ISO-9660 driver for the EDK2, you probably could do so. (IANAL,
though, so check the license information in each file and consult a
lawyer if you think it's necessary.) Oracle slapped GPL notices in some
of its files, and the versions I use in rEFInd are based on these, so
most of the VirtualBox and rEFInd files should not be used as a basis
for an EDK2 driver.
--
Rod Smith
rodsm...@rodsbooks.com
http://www.rodsbooks.com
------------------------------
Message: 2
Date: Wed, 16 Oct 2013 13:06:28 -0700
From: Blibbet <blib...@gmail.com>
Subject: Re: [edk2] NTFS partition driver and partition imaging
To: edk2-devel@lists.sourceforge.net
Message-ID: <525ef1c4.4020...@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks to all replies in this thread, useful information!
> Note that Apple's HFS+ EFI driver supplements, but does not
> replace, the FAT driver. If Apple had replaced the FAT driver with an
> HFS+ driver, it would have just made it harder to install other EFI-mode
> OSes on their hardware.
It would be nice if Apple had a separate HFS+ driver, and made the
binary available like the FAT one is, for use in UDK-derived projects,
even with additional licensing/restrictions if necessary.
> [...] Oracle took it up and released a finished version as
> part of VirtualBox (https://www.virtualbox.org). I also distribute a
> slightly modified version of this driver with rEFInd
> (http://www.rodsbooks.com/refind/). [...]
Thanks, nice to know. (And excellent web site, BTW.)
Could you clarify how the two versions of ISO 9660 drivers differ, how
rEFInd behaves from VirtualBox?
Thanks.
------------------------------
Message: 3
Date: Wed, 16 Oct 2013 17:18:42 -0400
From: Rod Smith <rodsm...@rodsbooks.com>
Subject: Re: [edk2] NTFS partition driver and partition imaging
To: edk2-devel@lists.sourceforge.net
Message-ID: <525f02b2.20...@rodsbooks.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 10/16/2013 04:06 PM, Blibbet wrote:
> Thanks to all replies in this thread, useful information!
>
> > Note that Apple's HFS+ EFI driver supplements, but does not
> > replace, the FAT driver. If Apple had replaced the FAT driver with an
> > HFS+ driver, it would have just made it harder to install other EFI-mode
> > OSes on their hardware.
>
> It would be nice if Apple had a separate HFS+ driver, and made the
> binary available like the FAT one is, for use in UDK-derived projects,
> even with additional licensing/restrictions if necessary.
There's a GPL-licensed Oracle HFS+ driver, which is also available with
rEFInd. As with the ISO-9660 driver, that could not be included directly
with the EDK2 for licensing reasons, but you can use it separately, if
you like....
> > [...] Oracle took it up and released a finished version as
> > part of VirtualBox (https://www.virtualbox.org). I also distribute a
> > slightly modified version of this driver with rEFInd
> > (http://www.rodsbooks.com/refind/). [...]
>
> Thanks, nice to know. (And excellent web site, BTW.)
>
> Could you clarify how the two versions of ISO 9660 drivers differ, how
> rEFInd behaves from VirtualBox?
I haven't studied the code in detail, and I've never tried the original
rEFIt version of the ISO-9660 driver. Based on comments in the code, it
sounds like the rEFIt driver has a number of limitations that have been
lifted in the Oracle version of the driver. I recommend you study the
code and/or try to compile both versions yourself if you need more
information.
rEFInd itself works fine from VirtualBox (with EFI support enabled, of
course). Because VirtualBox has its ISO-9660 driver compiled into its
EFI, the rEFInd ISO-9660 driver doesn't do anything under VirtualBox.
--
Rod Smith
rodsm...@rodsbooks.com
http://www.rodsbooks.com
------------------------------
Message: 4
Date: Thu, 17 Oct 2013 18:24:54 +0530
From: <parmeshwr_pra...@dell.com>
Subject: [edk2] problem in openprotocol
To: <edk2-devel@lists.sourceforge.net>
Message-ID:
<eaec0bcd44614f499e7cce37c3b71f11372b2f7...@blrx7mcdc202.amer.dell.com>
Content-Type: text/plain; charset="us-ascii"
Hi all,
I am working on some project where I need to open Disk protocol.
Below is my code-
Status = gBS->OpenProtocol(ControllerHandle
,&gEfiDiskIoProtocolGuid,(VOID **) &DiskIo, gImageHandle, NULL,
EFI_OPEN_PROTOCOL_BY_DRIVER);
if (EFI_ERROR(Status)) {
Print(L"Disk IO error %d\n",Status);
return Status;
}
Why this code always goes to error condition.
If I use EFI_OPEN_PROTOCOL_GET_PROTOCOL as parameter it will not go to error
condition, how to get rid of this problem ?
Best Regards,
Parmeshwr Prasad
[cid:image001.png@01CECB66.2CFA58B0]
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6104 bytes
Desc: image001.png
------------------------------
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
------------------------------
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
End of edk2-devel Digest, Vol 46, Issue 34
******************************************------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
