From: Trilok Soni <quic_tsoni@quicinc.com>
To: Nikunj Kela <quic_nkela@quicinc.com>
Cc: <agross@kernel.org>, <andersson@kernel.org>, <kernel@quicinc.com>,
<konrad.dybcio@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <psodagud@quicinc.com>,
<quic_aneelaka@quicinc.com>, <quic_kprasan@quicinc.com>,
<quic_ninanaik@quicinc.com>, <quic_ppareek@quicinc.com>
Subject: Re: [RFC PATCH 0/1] Add driver to read secondary bootloader (XBL) log
Date: Tue, 12 Sep 2023 09:11:57 -0700 [thread overview]
Message-ID: <bd3ccb8f-0341-879b-113b-50b341e00d4d@quicinc.com> (raw)
In-Reply-To: <20230912160800.39412-1-quic_nkela@quicinc.com>
On 9/12/2023 9:08 AM, Nikunj Kela wrote:
> From: Nikunj Kela <quic_nkela@quicinc.com
>
> I was planning something similar for dumping firmware VM's logs. These are in
> ascii format too hence doesn't require any parsing/post processing. Can this
> be little generic so I can use this driver?
This is exactly I want to avoid too. The discussion internally lead us to look at the UEFI/EDK2 work done by Alexander Graf [1] and TPM EFI log driver. For EDK2 we should have generic approach coming from the EDK2 and not just SOC vendor specific approaches.
[1]
https://edk2.groups.io/g/devel/message/90067
https://github.com/agraf/linux/commit/b1fe0c296ec923e9b1f544862b0eb9365a8da7cb
--
---Trilok Soni
prev parent reply other threads:[~2023-09-12 16:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 12:15 Ninad Naik
2023-08-22 12:15 ` [RFC PATCH 1/1] soc: qcom: " Ninad Naik
2023-08-22 12:39 ` Pavan Kondeti
2023-08-23 11:06 ` Ninad Naik
2023-08-22 12:43 ` Bryan O'Donoghue
2023-08-22 15:14 ` Jeff Johnson
2023-08-23 11:08 ` Ninad Naik
2023-08-23 11:08 ` Ninad Naik
2023-08-22 13:41 ` Srinivas Kandagatla
2023-08-23 11:09 ` Ninad Naik
2023-08-22 16:08 ` Trilok Soni
2023-08-23 11:16 ` Ninad Naik
2023-08-23 19:32 ` Trilok Soni
2023-08-28 17:19 ` [RFC PATCH 0/1] " Arun Kumar Neelakantam
2023-08-28 18:44 ` Trilok Soni
2023-08-28 19:20 ` Bjorn Andersson
2023-09-12 16:08 ` Nikunj Kela
2023-09-12 16:11 ` Trilok Soni [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-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=bd3ccb8f-0341-879b-113b-50b341e00d4d@quicinc.com \
--to=quic_tsoni@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=psodagud@quicinc.com \
--cc=quic_aneelaka@quicinc.com \
--cc=quic_kprasan@quicinc.com \
--cc=quic_ninanaik@quicinc.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_ppareek@quicinc.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®