英文練習

Type of Image(映像檔類型)	Description(註解)
Application(應用程式)	An EFI image of type EFI_IMAGE_SUBSYSTEM_EFI_APPLICATION. 一種EFI_IMAGE_SUBSYSTEM_EFI_APPLICATION類型的EFI映像檔(EFI image)。 This image is executed and automatically unloaded when the image exits or returns from its entry point. 這種映像檔會被執行，以及在結束或是它的進入點函式(entry point)回傳結果後被卸載。
OS loader(作業系統載入器)	A special type of application that normally does not return or exit. 這是一種特殊的應用程式，通常不會回傳結果或是結束。 Instead, it calls the EFI Boot Service gBS->ExitBootServices() to transfer control of the platform from the firmware to an operating system. 相反地，它會呼叫開機時期系統服務gBS->ExitBootServices()，將系統平台的控制權從韌體轉移到OS。
Driver(驅動程式)	An EFI image of type EFI_IMAGE_SUBSYSTEM_BOOT_SERVICE_DRIVER or EFI_IMAGE_SUBSYSTEM_RUNTIME_DRIVER. EFI_IMAGE_SUBSYSTEM_BOOT_SERVICE_DRIVER或EFI_IMAGE_SUBSYSTEM_RUNTIME_DRIVER類型的EFI映像檔(EFI image)。 If this image returns EFI_SUCCESS, then the image is not unloaded. 如果這個映像檔回傳EFI_SUCCESS，那麼此映像檔不會被卸載。 If the image returns an error code other than EFI_SUCCESS, then the image is automatically unloaded from system memory. 如果這個映像檔回傳EFI_SUCCESS之外的其他錯誤代碼，那麼此映像檔會自動從系統記憶體中被卸載。 The ability to stay resident in system memory is what differentiates a driver from an application. 驅動程式與應用程式的不同在於，常駐於系統記憶體的能力。 Because drivers can stay resident in memory, they can provide services to other drivers, applications, or an operating system. 因為驅動程式可以常駐於系統記憶體，所以可以提供系統服務其他的驅動程式、應用程式或作業系統。 Only the services produced by runtime drivers are allowed to persist past gBS->ExitBootServices(). 只有運行時期的驅動程式所產生的系統服務，允許保留到gBS->ExitBootServices()執行之後。
Service driver(系統驅動程式)	A driver that produces one or more protocols on one or more new service handles and returns EFI_SUCESS from its entry point. 驅動程式會產生一個以上的protocols在一個以上的新的service handles，以及在它的進入點函式(entry point)回傳EFI_SUCESS。
Initializing driver(初始化驅動程式)	A driver that does not create any handles and does not add any protocols to the handle database. 一個驅動程式不能創建任何的handles，也不能將任何的protocols加入到handle database中。 Instead, this type of driver performs some initialization operations and returns an error code so the driver is unloaded from system memory. 相反地，驅動程式之類會運行一些初始化操作，以及回傳錯誤代碼，如此驅動程式就會從系統記憶體中被卸載。
Root bridge driver(根源橋接器驅動程式)	A driver that creates one or physical controller handles that contain a Device Path Protocol and a protocol that is a software abstraction for the I/O services provided by a root bus produced by a core chipset. 一個驅動程式創建一個或物理的控制器資源表(controller handles)，它包含了Device Path Protocol，以及軟體抽象化核心晶片組所產生的源頭匯流排所提供的I/O 系統服務的protocol。 The most common root bridge driver is one that creates handles for the PCI root bridges in the platform that support the Device Path Protocol and the PCI Root Bridge I/O Protocol. 最普遍的源頭橋接器驅動程式(root bridge driver)就是在支援Device Path Protocol與PCI Root Bridge I/O Protocol的系統平台上的PCI源頭橋接器(PCI root bridges)。
EFI 1.02 driver	A driver that follows the EFI 1.02 Specification. 遵守EFI 1.02版規範的驅動程式。 This type of driver does not use the EFI Driver Model. 不使用EFI Driver Model的驅動程式類型。 These types of drivers are not discussed in detail in this document. 在本書中不會討論這種驅動程式的細節。 Instead, this document presents recommendations on converting EFI 1.02 drivers to drivers that follow the EFI Driver Model. 相反地，本書會建議將EFI 1.02 驅動程式轉換為符合EFI驅動模型(EFI Driver Model)的驅動程式
EFI Driver Model(EFI驅動模組) driver	A driver that follows the EFI Driver Model that is described in detail in the EFI 1.10 Specification. 這種驅動程式是遵循定義在EFI 1.10規範中的EFI驅動模組(EFI Driver Model)。 This type of driver is fundamentally different from service drivers, initializing drivers, root bridge drivers, and EFI 1.02 drivers because a driver that follows the EFI Driver Model is not allowed to touch hardware or produce device-related services in the driver entry point. 這種驅動程式基本上與系統服務(service drivers)、初始化驅動程式(initializing drivers)、來源橋接器(root bridge drivers)以及EFI 1.02版驅動程式(EFI 1.02 drivers)不同，因為它是遵循EFI驅動模組(EFI Driver Model)的規範，它不被允許在進入點函式(entry point)中直接接觸硬體或是產生與裝置相關的系統服務。 Instead, the driver entry point of a driver that follows the EFI Driver Model is allowed only to register a set of services that allow the driver to be started and stopped at a later point in the system initialization process. 相反地，按照EFI驅動模組(EFI Driver Model)的規範，驅動程式的進入點函式(entry point)只可以註冊系統服務，它允許驅動程式在系統初始化的過程的晚期可以被啟動或停止。 Note: 1.看來EFI Driver Model就像是一層抽象層的驅動程式，企圖抽象化硬體層，使得整體系統的上層可以與實體層脫勾。
Device driver(設備驅動程式)	A driver that follows the EFI Driver Model. 這是一種遵守EFI驅動模組(EFI Driver Model)規範的驅動程式。 This type of driver produces one or more driver handles or driver image handles by installing one or more instances of the Driver Binding Protocol into the handle database. 這種類型的驅動程式會產生一個以上的驅動程式資源表(driver handles)或是驅動程式映像檔資源表(driver image handles)，透過安裝一個以上的Driver Binding Protocol，存入系統資源庫(handle database)中。 This type of driver does not create any child handles when the Start() service of the Driver Binding Protocol is called. 這種類型的驅動程式在Driver Binding Protocol的Start()系統服務被呼叫時，不會產生任何的子端系統資源表(child handles)。 Instead, it only adds additional I/O protocols to existing controller handles. 相反地，它只會附加上I/O protocols到目前的控制器資源表上。
Bus driver(匯流排驅動程式)	A driver that follows the EFI Driver Model. 這是一種遵守EFI驅動模組(EFI Driver Model)規範的驅動程式。 This type of driver produces one or more driver handles or driver image handles by installing one or more instances of the Driver Binding Protocol in the handle database. 這種類型的驅動程式會產生一個以上的驅動程式資源表(driver handles)或是驅動程式映像檔資源表(driver image handles)，透過安裝一個以上的Driver Binding Protocol，存入系統資源庫(handle database)中。 This type of driver creates new child handles when the Start() service of the Driver Binding Protocol is called. 這種類型的驅動程式在Driver Binding Protocol的Start()系統服務被呼叫時，會產生新的子端系統資源表(child handles)。 It also adds I/O protocols to these newly created child handles. 同時會將I/O protocols加入到新創建的子端系統資源表(child handles)中。
Hybrid driver(混合式驅動程式)	A driver that follows the EFI Driver Model and shares characteristics with both device drivers and bus drivers. 這是一種遵守EFI驅動模組(EFI Driver Model)規範的驅動程式，而且同時擁有設備驅動程式(device drivers)與匯流排驅動程式(bus drivers)兩者的特性。 This distinction means that the Start() service of the Driver Binding Protocol will add I/O protocols to existing handles and it will create child handles. 它的不同之處在於Driver Binding Protocol的Start()系統服務被呼叫時，會將I/O protocols加到目前的資源表中，同時會創建新的子端系統資源表(child handles)。