From: Laszlo Ersek <lersek@redhat.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Wang, Jian J" <jian.j.wang@intel.com>,
"Justen, Jordan L" <jordan.l.justen@intel.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: ASSERT in QemuVideoDxe driver during reset
Date: Wed, 6 Sep 2017 17:35:36 +0200 [thread overview]
Message-ID: <1d35637f-5a6f-702e-09a2-2bf9f3b45b32@redhat.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14D78AF1E@shsmsx102.ccr.corp.intel.com>
On 09/06/17 16:47, Gao, Liming wrote:
> Laszlo:
>
>> * Independently: if the CSM too conflicts with the null detection
>> feature, then we should probably report an "unsupported configuration"
>> error for the following case:
>>
>> -D NULL_DETECT_ENABLE -D CSM_ENABLE
>>
>> But, I don't know if triggering build errors, with custom error
>> messages, is possible in DSC files.
>
> Now, there is no support to report the error message for the invalid combination. I think this is a good request to BaseTools. We can introduce !error "error message" syntax in DSC/FDF. If the invalid combination happen, !error will trig build error message. Could you help submit this feature request in BugZillar?
Thank you very much for considering it; I've filed:
https://bugzilla.tianocore.org/show_bug.cgi?id=701
Laszlo
next prev parent reply other threads:[~2017-09-06 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 8:15 ASSERT in QemuVideoDxe driver during reset Wang, Jian J
2017-09-06 10:20 ` Laszlo Ersek
2017-09-06 11:16 ` Yao, Jiewen
2017-09-06 13:18 ` Laszlo Ersek
2017-09-06 14:47 ` Gao, Liming
2017-09-06 15:35 ` Laszlo Ersek [this message]
2017-09-06 15:06 ` Yao, Jiewen
2017-09-06 15:25 ` Laszlo Ersek
2017-09-07 0:54 ` Yao, Jiewen
2017-09-07 0:41 ` Wang, Jian J
2017-09-07 1:28 ` Yao, Jiewen
2017-09-07 10:58 ` Laszlo Ersek
2017-09-07 11:16 ` Yao, Jiewen
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=1d35637f-5a6f-702e-09a2-2bf9f3b45b32@redhat.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