sravan/system76-edk2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Change many windows references to unix.

Browse Source 
git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@2186 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
bbahnsen
2007-01-07 19:31:19 +00:00
parent 6bb60d710b
commit 377fc2ae71
29 changed files with 62 additions and 62 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
EdkUnixPkg/Dxe/UnixThunk/Bus/BlockIo/UnixBlockIo.c
View File

@@ -15,8 +15,8 @@ Module Name:
Abstract:
Produce block IO abstractions for real devices on your PC using Win32 APIs.
The configuration of what devices to mount or emulate comes from NT
Produce block IO abstractions for real devices on your PC using Posix APIs.
The configuration of what devices to mount or emulate comes from UNIX
environment variables. The variables must be visible to the Microsoft*
Developer Studio for them to work.
@@ -27,7 +27,7 @@ Abstract:
<block count> - Decimal number of blocks a device supports.
<block size> - Decimal number of bytes per block.
NT envirnonment variable contents. '<' and '>' are not part of the variable,
UNIX envirnonment variable contents. '<' and '>' are not part of the variable,
they are just used to make this help more readable. There should be no
spaces between the ';'. Extra spaces will break the variable. A '!' is
used to seperate multiple devices in a variable.
@@ -47,7 +47,7 @@ Abstract:
A 1.44MB emulated floppy with a block size of 1024 would look like:
EFI_UNIX_VIRTUAL_DISKS=RW;1440;1024
Physical Disks: These devices use NT to open a real device in your system
Physical Disks: These devices use UNIX to open a real device in your system
Thus a 120 MB floppy would look like:
EFI_UNIX_PHYSICAL_DISKS=B:RW;245760;512

4
EdkUnixPkg/Dxe/UnixThunk/Bus/BlockIo/UnixBlockIo.h
View File

@@ -15,8 +15,8 @@ Module Name:
Abstract:
Produce block IO abstractions for real devices on your PC using Win32 APIs.
The configuration of what devices to mount or emulate comes from NT
Produce block IO abstractions for real devices on your PC using Posix APIs.
The configuration of what devices to mount or emulate comes from UNIX
environment variables. The variables must be visible to the Microsoft*
Developer Studio for them to work.

2
EdkUnixPkg/Dxe/UnixThunk/Bus/Console/Console.c
View File

@@ -15,7 +15,7 @@ Module Name:
Abstract:
Console based on Win32 APIs.
Console based on Posix APIs.
--*/

4
EdkUnixPkg/Dxe/UnixThunk/Bus/Console/Console.h
View File

@@ -15,7 +15,7 @@ Module Name:
Abstract:
Console based on Win32 APIs.
Console based on Posix APIs.
This file attaches a SimpleTextIn protocol to a previously open window.
@@ -44,7 +44,7 @@ typedef struct {
EFI_UNIX_THUNK_PROTOCOL *UnixThunk;
//
// SimpleTextOut Private Data including Win32 types.
// SimpleTextOut Private Data including Posix types.
//
// HANDLE NtOutHandle;
// HANDLE NtInHandle;

2
EdkUnixPkg/Dxe/UnixThunk/Bus/Console/ConsoleIn.c
View File

@@ -15,7 +15,7 @@ Module Name:
Abstract:
Console based on Win32 APIs.
Console based on Posix APIs.
This file attaches a SimpleTextIn protocol to a previously open window.

4
EdkUnixPkg/Dxe/UnixThunk/Bus/Console/ConsoleOut.c
View File

@@ -15,9 +15,9 @@ Module Name:
Abstract:
Console based on Win32 APIs.
Console based on Posix APIs.
This file creates an Win32 window and attaches a SimpleTextOut protocol.
This file creates an Posix window and attaches a SimpleTextOut protocol.
--*/

8
EdkUnixPkg/Dxe/UnixThunk/Bus/SimpleFileSystem/UnixSimpleFileSystem.c
View File

@@ -15,8 +15,8 @@ Module Name:
Abstract:
Produce Simple File System abstractions for directories on your PC using Win32 APIs.
The configuration of what devices to mount or emulate comes from NT
Produce Simple File System abstractions for directories on your PC using Posix APIs.
The configuration of what devices to mount or emulate comes from UNIX
environment variables. The variables must be visible to the Microsoft*
Developer Studio for them to work.
@@ -1398,7 +1398,7 @@ Returns:
return EFI_SUCCESS;
//
// bugbug: need to access windows error reporting
// bugbug: need to access unix error reporting
//
}
@@ -2100,7 +2100,7 @@ Returns:
return PrivateFile->UnixThunk->FSync (PrivateFile->fd) == 0 ? EFI_SUCCESS : EFI_DEVICE_ERROR;
//
// bugbug: - Use Windows error reporting.
// bugbug: - Use Unix error reporting.
//
}

2
EdkUnixPkg/Dxe/UnixThunk/Bus/Uga/UnixUga.h
View File

@@ -136,7 +136,7 @@ Returns:
;
//
// EFI 1.1 driver model prototypes for Win NT UGA
// EFI 1.1 driver model prototypes for Win UNIX UGA
//
EFI_STATUS

10
EdkUnixPkg/Dxe/UnixThunk/Bus/UnixBusDriver/UnixBusDriver.c
View File

@@ -15,9 +15,9 @@ Module Name:
Abstract:
This following section documents the envirnoment variables for the Win NT
This following section documents the envirnoment variables for the Win UNIX
build. These variables are used to define the (virtual) hardware
configuration of the NT environment
configuration of the UNIX environment
A ! can be used to seperate multiple instances in a variable. Each
instance represents a seperate hardware device.
@@ -35,7 +35,7 @@ EFI_UNIX_UGA - Builds UGA Windows of Width and Height
<block count> - Decimal number of blocks a device supports.
<block size> - Decimal number of bytes per block.
NT envirnonment variable contents. '<' and '>' are not part of the variable,
UNIX envirnonment variable contents. '<' and '>' are not part of the variable,
they are just used to make this help more readable. There should be no
spaces between the ';'. Extra spaces will break the variable. A '!' is
used to seperate multiple devices in a variable.
@@ -55,7 +55,7 @@ EFI_UNIX_UGA - Builds UGA Windows of Width and Height
A 1.44MB emulated floppy with a block size of 1024 would look like:
EFI_UNIX_VIRTUAL_DISKS=RW;1440;1024
Physical Disks: These devices use NT to open a real device in your system
Physical Disks: These devices use UNIX to open a real device in your system
Thus a 120 MB floppy would look like:
EFI_UNIX_PHYSICAL_DISKS=B:RW;245760;512
@@ -115,7 +115,7 @@ EFI_DRIVER_BINDING_PROTOCOL gUnixBusDriverBinding = {
#define UNIX_PCD_ARRAY_SIZE (sizeof(mPcdEnvironment)/sizeof(UNIX_PCD_ENTRY))
//
// Table to map NT Environment variable to the GUID that should be in
// Table to map UNIX Environment variable to the GUID that should be in
// device path.
//
static UNIX_PCD_ENTRY mPcdEnvironment[] = {

4
EdkUnixPkg/Dxe/UnixThunk/Bus/UnixBusDriver/UnixBusDriver.h
View File

@@ -37,7 +37,7 @@ EFI_UNIX_PASS_THRU - associates a device with our PCI support
<block count> - Decimal number of blocks a device supports.
<block size> - Decimal number of bytes per block.
NT envirnonment variable contents. '<' and '>' are not part of the variable,
UNIX envirnonment variable contents. '<' and '>' are not part of the variable,
they are just used to make this help more readable. There should be no
spaces between the ';'. Extra spaces will break the variable. A '!' is
used to seperate multiple devices in a variable.
@@ -57,7 +57,7 @@ EFI_UNIX_PASS_THRU - associates a device with our PCI support
A 1.44MB emulated floppy with a block size of 1024 would look like:
EFI_UNIX_VIRTUAL_DISKS=RW;1440;1024
Physical Disks: These devices use NT to open a real device in your system
Physical Disks: These devices use UNIX to open a real device in your system
Thus a 120 MB floppy would look like:
EFI_UNIX_PHYSICAL_DISKS=B:RW;245760;512

2
EdkUnixPkg/Dxe/UnixThunk/Bus/UnixBusDriver/UnixBusDriver.msa
View File

@@ -132,7 +132,7 @@
<PcdEntry PcdItemType="DYNAMIC">
<C_Name>PcdUnixFileSystem</C_Name>
<TokenSpaceGuidCName>gEfiEdkUnixPkgTokenSpaceGuid</TokenSpaceGuidCName>
<HelpText>This PCD defines the windows directory who will be mounted as
<HelpText>This PCD defines the unix directory who will be mounted as
harddisk in simulator.
The item type of this PCD can only be "DYNAMIC".</HelpText>
</PcdEntry>