Re: difference between asm16 and asm files

["Tiger Liu(BJ-RD)" <TigerLiu@zhaoxin.com>]

Hi, Liming:
Got it!

Thanks

Best wishes,

-----邮件原件-----
发件人: Gao, Liming [mailto:liming.gao@intel.com]
发送时间: 2018年1月31日 17:44
收件人: Tiger Liu(BJ-RD) <TigerLiu@zhaoxin.com>; edk2-devel@lists.01.org
主题: RE: [edk2] difference between asm16 and asm files

Tiger:
  Nasm compiler supports to generate 16bit raw code. User doesn't need to install the additional tool. And, the raw code is 16bit code. You need 16bit assembler. It is also nasm compiler. So, it is obvious to use nasm to directly do it.

Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Tiger Liu(BJ-RD)
>Sent: Wednesday, January 31, 2018 1:18 PM
>To: Gao, Liming <liming.gao@intel.com>; edk2-devel@lists.01.org
>Subject: Re: [edk2] difference between asm16 and asm files
>
>Hi, Liming:
>YES, its code need to be the raw execution code.
>I mean:
>1. We could use traditional asm code , compiled it, and use tools to
>translate them to the raw execution code.
>Is there any difficulty to do this?
>
>So, it would depreciate the asm16 or nasmb concept.
>
>Thanks
>-----邮件原件-----
>发件人: Tiger Liu(BJ-RD)
>发送时间: 2018年1月30日 9:45
>收件人: 'Gao, Liming' <liming.gao@intel.com>; edk2-devel@lists.01.org
>主题: Re: [edk2] difference between asm16 and asm files
>
>Hi, Liming:
>Thanks for your reply!
>
>I have another question:
>Why not let sec code complied to obj file and linked to lib and EFI image?
>
>I met a problem:
>I tried to use IFDEF marco in an assembly inc file,  and this inc file
>would be included by ResetVec.asm16 But failed, it seemed asm 16
>complier not recognize this marco exist.
>If I changed ResetVec.asm16 to ResetVec.asm, and compiled again, the
>complier will recognize this marco exist.
>But the last step failed, GenFds.exe seems search a binary file, and not found.
>
>Thanks
>-----邮件原件-----
>发件人: Gao, Liming [mailto:liming.gao@intel.com]
>发送时间: 2018年1月29日 22:30
>收件人: Tiger Liu(BJ-RD) <TigerLiu@zhaoxin.com>; edk2-devel@lists.01.org
>主题: RE: [edk2] difference between asm16 and asm files
>
>Asm16 is compiled to the binary file. Asm is compiled to the obj file,
>and linked into lib and EFI image.
>
>Now, asm16 is replaced by nasmb. Asm is replaced by nasm. If you check
>SecCore.inf, you will find ResetVec.asm16 is not used, and
>ResetVec.nasmb is used. I will send the patch to remove the unused
>ResetVec.asm16 to avoid the confuse.
>
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf
>> Of Tiger Liu(BJ-RD)
>> Sent: Monday, January 29, 2018 6:49 PM
>> To: edk2-devel@lists.01.org
>> Subject: [edk2] difference between asm16 and asm files
>>
>> Hi, experts:
>> I have a question about asm16 postfix and asm postfix.
>>
>> Such as:
>> UefiCpuPkg\SecCore\Ia32\ResetVec.asm16
>>
>> Why not use asm as postfix?
>>
>> Thanks
>>
>> Best wishes,
>>
>>
>> ?????
>> ?????????????????????????????????????????????????????
>> CONFIDENTIAL NOTE:
>> This email contains confidential or legally privileged information
>> and is for the sole use of its intended recipient. Any unauthorized
>> review, use,
>copying or forwarding of this email or the content of this email is
>strictly prohibited.
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
>
>
>保密声明：
>本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其
>内容做任何未经授权的查阅、使用、复制或转发。
>CONFIDENTIAL NOTE:
>This email contains confidential or legally privileged information and
>is for the sole use of its intended recipient. Any unauthorized review,
>use, copying or forwarding of this email or the content of this email is strictly prohibited.
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel


保密声明：
本邮件含有保密或专有信息，仅供指定收件人使用。严禁对本邮件或其内容做任何未经授权的查阅、使用、复制或转发。
CONFIDENTIAL NOTE:
This email contains confidential or legally privileged information and is for the sole use of its intended recipient. Any unauthorized review, use, copying or forwarding of this email or the content of this email is strictly prohibited.