From: Jon Masters <jcm@jonmasters.org>
To: "Wang, Dongsheng" <dongsheng.wang@hxt-semitech.com>,
Hanjun Guo <guohanjun@huawei.com>,
"Yang, Shunyong" <shunyong.yang@hxt-semitech.com>,
"rjw@rjwysocki.net" <rjw@rjwysocki.net>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zheng, Joey" <yu.zheng@hxt-semitech.com>,
"Jiang, Yutang2" <yutang2.jiang@hxt-semitech.com>
Subject: Re: [PATCH v3] ACPI / tables: Add IORT to injectable table list
Date: Mon, 19 Feb 2018 14:13:38 -0500 [thread overview]
Message-ID: <669340a4-e748-07f4-51d5-bf0566cd75b8@jonmasters.org> (raw)
In-Reply-To: <em5890c25f-84af-42ac-bfea-b27c6516e46b@bjl0091>
On 02/02/2018 07:12 AM, Wang, Dongsheng wrote:
> Hey, Hanjun,
>
> On 2018/2/2 19:54:24, "Hanjun Guo" <guohanjun@huawei.com> wrote:
>
>> On 2018/2/2 18:25, Yang Shunyong wrote:
>>> Loading IORT table from initrd is used to fix firmware IORT defects.
>>
>> I don't think this fix "firmware defects", it just for debug purpose,
>> we will not use that for production purpose, right? I think above line
>> can be removed.
>>
> I thinks the upgrade feature not only for debug. Here's an important
> way to fix bugs that come from the firmware.
>
> Documentation/acpi/initrd_table_override.txt
I think we should message that this is for debug/development use.
Ultimately, it's not the way to address firmware problems. Firmware
needs to address that by shipping the correct(ed) tables :)
--
Computer Architect
next prev parent reply other threads:[~2018-02-19 19:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 10:25 Yang Shunyong
2018-02-02 11:54 ` Hanjun Guo
2018-02-02 12:12 ` Wang, Dongsheng
2018-02-19 19:13 ` Jon Masters [this message]
2018-02-20 2:52 ` Yang, Shunyong
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-all 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=669340a4-e748-07f4-51d5-bf0566cd75b8@jonmasters.org \
--to=jcm@jonmasters.org \
--cc=dongsheng.wang@hxt-semitech.com \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shunyong.yang@hxt-semitech.com \
--cc=yu.zheng@hxt-semitech.com \
--cc=yutang2.jiang@hxt-semitech.com \
/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
all inboxes | Powered by JetHome®