Author: stepan Date: 2009-04-22 00:05:50 +0200 (Wed, 22 Apr 2009) New Revision: 4156
Modified: trunk/coreboot-v2/documentation/LinuxBIOS-AMD64.tex Log: small updates as suggested by Carl-Daniel Hailfinger.
Signed-off-by: Stefan Reinauer stepan@coresystems.de Acked-by: Stefan Reinauer stepan@coresystems.de
Modified: trunk/coreboot-v2/documentation/LinuxBIOS-AMD64.tex =================================================================== --- trunk/coreboot-v2/documentation/LinuxBIOS-AMD64.tex 2009-04-21 21:45:11 UTC (rev 4155) +++ trunk/coreboot-v2/documentation/LinuxBIOS-AMD64.tex 2009-04-21 22:05:50 UTC (rev 4156) @@ -514,7 +514,7 @@ \item \begin{verbatim}driver\end{verbatim}
The \texttt{driver} keyword adds an object file to the driver section of a -coreboot�image. This means it can be used by the PCI device +coreboot image. This means it can be used by the PCI device initialization code. Example:
\begin{verbatim} @@ -1523,7 +1523,8 @@
\section{Image types} There used to be one image type for coreboot, as described above. Since this paper was written (2004) there have been many changes. First, the name -was changed to coreboot, for many reasons. Second, Ying-Hai Liu, then of AMD, now of Sun, added Cache As Ram support (CAR) for many AMD CPUs, which both simplified and complicated things. Simplification came with the removal of romcc; complication came with the addition of new ways to build. +was changed to coreboot, for many reasons. Second, Cache As Ram support (CAR) +was added for many AMD CPUs, which both simplified and complicated things. Simplification came with the removal of romcc; complication came with the addition of new ways to build.
There are two big additions to the build process and, furthermore, more than two new CONFIG variables to control them.