archive-gh-me/OpenCorePkg
1
0
Fork 0
mirror of https://github.com/acidanthera/OpenCorePkg.git synced 2025-12-08 19:25:01 +00:00
Code Issues Projects Releases Wiki Activity

Docs: Minor fixes

Browse Source
This commit is contained in:
Mike Beaton 2023-05-06 08:53:31 +01:00
parent c4c8e3412a
commit 0c7caaee4b
6 changed files with 17 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Docs/Configuration.md5
View File

@ -1 +1 @@
a9d2c3cb363b987aa240e1e08f207276
afa5c5a664cf02fad646b6f259ddba2d

BIN
Docs/Configuration.pdf
View File

Binary file not shown.

12
Docs/Configuration.tex
View File

@ -8123,8 +8123,8 @@ for additional options.
do not provide a native \texttt{ConsoleControl} and rendering modes. OpenCore
and macOS expect text to only be shown in \texttt{Text} mode but
graphics to be drawn in any mode, and this is how the OpenCore \texttt{Builtin}
renderer behaves. Since this is not required by UEFI specification, behaviour
of the system \texttt{ConsoleControl} protocol, when it exists, varies.
renderer behaves. Since this is not required by the UEFI specification, behaviour
of the system \texttt{ConsoleControl} protocol, when it exists, may vary.
\item
\texttt{TextRenderer}\\
@ -8134,11 +8134,11 @@ for additional options.
console output.
Currently two renderers are supported: \texttt{Builtin} and
\texttt{System}. \texttt{System} renderer uses firmware services
\texttt{System}. The \texttt{System} renderer uses firmware services
for text rendering, however with additional options provided to
santize the output. \texttt{Builtin} renderer bypasses firmware
sanitize the output. The \texttt{Builtin} renderer bypasses firmware
services and performs text rendering on its own. Each renderer
supports a different set of options. It is recommended to use
supports a different set of options. It is recommended to use the
\texttt{Builtin} renderer, as it supports HiDPI mode and uses
full screen resolution.
@ -8151,7 +8151,7 @@ for additional options.
and the \texttt{ConsoleControl} mode to set on the underlying system
\texttt{ConsoleControl} protocol before starting. To control the initial
mode of the provided \texttt{ConsoleControl} protocol once started, use
the \texttt{InitalMode} option.
the \texttt{InitialMode} option.
\begin{itemize}
\tightlist

BIN
Docs/Differences/Differences.pdf
View File

Binary file not shown.

20
Docs/Differences/Differences.tex
View File

@ -1,7 +1,7 @@
\documentclass[]{article}
%DIF LATEXDIFF DIFFERENCE FILE
%DIF DEL PreviousConfiguration.tex Thu Apr 27 23:04:46 2023
%DIF ADD ../Configuration.tex Thu May 4 09:59:29 2023
%DIF DEL PreviousConfiguration.tex Mon Apr 24 10:37:10 2023
%DIF ADD ../Configuration.tex Sat May 6 08:47:24 2023
\usepackage{lmodern}
\usepackage{amssymb,amsmath}
@ -8195,8 +8195,8 @@ for additional options.
do not provide a native }\texttt{\DIFadd{ConsoleControl}} \DIFadd{and rendering modes. OpenCore
and macOS expect text to only be shown in }\texttt{\DIFadd{Text}} \DIFadd{mode but
graphics to be drawn in any mode, and this is how the OpenCore }\texttt{\DIFadd{Builtin}}
\DIFadd{renderer behaves. Since this is not required by UEFI specification, behaviour
of the system }\texttt{\DIFadd{ConsoleControl}} \DIFadd{protocol, when it exists, varies.
\DIFadd{renderer behaves. Since this is not required by the UEFI specification, behaviour
of the system }\texttt{\DIFadd{ConsoleControl}} \DIFadd{protocol, when it exists, may vary.
}
\item
@ -8207,13 +8207,13 @@ for additional options.
console output.
Currently two renderers are supported: \texttt{Builtin} and
\texttt{System}. \texttt{System} renderer uses firmware services
for text rendering\DIFaddbegin \DIFadd{, however with additional options provided to
santize the output}\DIFaddend . \texttt{Builtin} \DIFdelbegin \DIFdel{bypassing }\DIFdelend \DIFaddbegin \DIFadd{renderer bypasses }\DIFaddend firmware
\texttt{System}. \DIFaddbegin \DIFadd{The }\DIFaddend \texttt{System} renderer uses firmware services
for text rendering\DIFdelbegin \DIFdel{. }\DIFdelend \DIFaddbegin \DIFadd{, however with additional options provided to
sanitize the output. The }\DIFaddend \texttt{Builtin} \DIFdelbegin \DIFdel{bypassing }\DIFdelend \DIFaddbegin \DIFadd{renderer bypasses }\DIFaddend firmware
services and performs text rendering on its own. \DIFdelbegin \DIFdel{Different renderers support
}\DIFdelend \DIFaddbegin \DIFadd{Each renderer
supports }\DIFaddend a different set of options. It is recommended to use
\texttt{Builtin} renderer, as it supports HiDPI mode and uses
supports }\DIFaddend a different set of options. It is recommended to use \DIFaddbegin \DIFadd{the
}\DIFaddend \texttt{Builtin} renderer, as it supports HiDPI mode and uses
full screen resolution.
\DIFdelbegin \DIFdel{UEFI firmware typically supports }\DIFdelend \DIFaddbegin \DIFadd{Each renderer provides its own }\DIFaddend \texttt{ConsoleControl} \DIFdelbegin \DIFdel{with two
@ -8236,7 +8236,7 @@ for additional options.
and the }\texttt{\DIFadd{ConsoleControl}} \DIFadd{mode to set on the underlying system
}\texttt{\DIFadd{ConsoleControl}} \DIFadd{protocol before starting. To control the initial
mode of the provided }\texttt{\DIFadd{ConsoleControl}} \DIFadd{protocol once started, use
the }\texttt{\DIFadd{InitalMode}} \DIFadd{option.
the }\texttt{\DIFadd{InitialMode}} \DIFadd{option.
}\DIFaddend
\begin{itemize}

BIN
Docs/Errata/Errata.pdf
View File

Binary file not shown.