Searched refs:mBFT (Results 1 – 8 of 8) sorted by relevance
34 static bool valid_mbft(const struct mBFT *mbft, size_t space) in valid_mbft()61 static void output_params(const struct mBFT *mbft) in output_params()157 if (valid_mbft((const struct mBFT *)ptr, end-ptr)) { in main()158 output_params((const struct mBFT *)ptr); in main()
211 const struct mBFT far *mbft; in MDISKCHK_FUNC_DECL()223 if (mbft->acpi.length != sizeof(struct mBFT)) in MDISKCHK_FUNC_DECL()227 for (i = 0; i < sizeof(struct mBFT); i++) in MDISKCHK_FUNC_DECL()271 const struct mBFT far *mbft; in MDISKCHK_FUNC_DECL()
32 struct mBFT;105 struct mBFT { struct
11 ; Portions copyright 2009 Shao Miller [El Torito code, mBFT, safe hook]138 ; immediately find out the particular parameters using the mBFT139 ; and MDI structures. This binary will have the offset to the mBFT140 ; in this field to begin with, so the installer knows where the mBFT142 ; will refill this field with the physical address of the mBFT for144 dd mBFT ; Offset from hook to the mBFT1066 mBFT:1068 dd ' ' ; ACPI signature ("mBFT")1070 ; to avoid an accidentally valid mBFT1079 ; The next field is mBFT-specific and filled-in by the installer[all …]
763 struct mBFT *mbft; in setup()1142 mbft = (struct mBFT *)(((const char *)hptr) + hptr->safe_hook.mbft); in setup()
274 pointer to a special MEMDISK structure called the "mBFT." The mBFT is the279 The mBFT is little more than an ACPI table to prefix MEMDISK's traditional285 There is a 1-byte checksum field which covers the length of the mBFT all293 pointer to the mBFT and gathers the RAM disk details from the included
56 typedef struct mBFT s_mbft;
411 * MEMDISK: generate the mBFT checksum correctly.434 * memdisk: fix the mBFT ACPI table.454 * MEMDISK: New "mBFT" ACPI table, by analogy with the iSCSI