From: "Wu, Hao A" <hao.a.wu@intel.com>
To: jabir <jabirm@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: More info on revision2 and revision3 of EFI_BLOCK_IO_PROTOCOL
Date: Mon, 14 Jan 2019 00:17:38 +0000 [thread overview]
Message-ID: <B80AF82E9BFB8E4FBD8C89DA810C6A093C87DDAB@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <CAPJUX+oeOx66K8MRBW2T85B_28kfbVggbuBYGLfxj7hwB6u5sA@mail.gmail.com>
Hi Jabir,
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> jabir
> Sent: Friday, January 11, 2019 4:17 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] More info on revision2 and revision3 of
> EFI_BLOCK_IO_PROTOCOL
>
> Hi All,
>
> EFI_BLOCK_IO_MEDIA has two new fields, LowestAlignedLba and
> LogicalBlocksPerPhysicalBlock, added in the revision2 and a field
> OptimalTransferLengthGranularity added in revision3 of
> EFI_BLOCK_IO_PROTOCOL.
> Couldn’t find more info from https://github.com/tianocore/edk2.
>
> Please help to understand how these fields are consumed by the system
> firmware?
Maybe you can check the latest UEFI Specification Version 2.7 (Errata A):
http://www.uefi.org/sites/default/files/resources/UEFI%20Spec%202_7_A%20Sept%206.pdf
Section 5.3.1, to see if you can get the information.
Best Regards,
Hao Wu
>
> typedef struct {
> UINT32 MediaId;
> BOOLEAN RemovableMedia;
> BOOLEAN MediaPresent;
> BOOLEAN LogicalPartition;
> BOOLEAN ReadOnly;
> BOOLEAN WriteCaching;
> UINT32 BlockSize;
> UINT32 IoAlign;
> EFI_LBA LastBlock;
> EFI_LBA LowestAlignedLba; //added in Revision 2
> UINT32 LogicalBlocksPerPhysicalBlock; //added in Revision 2
> UINT32 OptimalTransferLengthGranularity; // added in Revision 3
> } EFI_BLOCK_IO_MEDIA;
>
> Thanks,
> Jabir
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2019-01-14 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 8:17 More info on revision2 and revision3 of EFI_BLOCK_IO_PROTOCOL jabir
2019-01-14 0:17 ` Wu, Hao A [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B80AF82E9BFB8E4FBD8C89DA810C6A093C87DDAB@SHSMSX101.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox