From: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, vbendeb@chromium.org,
groeck@chromium.org, bleung@chromium.org, dtor@chromium.org,
gwendal@chromium.org, andy@infradead.org,
Collabora Kernel ML <kernel@collabora.com>,
Ayman Bagabas <ayman.bagabas@gmail.com>,
Darren Hart <dvhart@infradead.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jeremy Soller <jeremy@system76.com>,
Mattias Jacobsson <2pi@mok.nu>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Rajat Jain <rajatja@google.com>,
Yauhen Kharuzhy <jekhor@gmail.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform: x86: Add ACPI driver for ChromeOS
Date: Wed, 25 Mar 2020 15:38:28 -0700 [thread overview]
Message-ID: <6f90d8fa0301b19ddae3e7558df6408e23f4e04b.camel@linux.intel.com> (raw)
In-Reply-To: <e29d6279-d7e3-8164-3f52-5017bfe79436@collabora.com>
On Wed, 2020-03-25 at 22:54 +0100, Enric Balletbo i Serra wrote:
> Hi Srinivas,
>
[cut]
> Evaluating \CRHW.HWID
> 0x1 Outstanding allocations after evaluation of \CRHW.HWID
> Evaluation of \CRHW.HWID returned object 0x55b9e373fd60, external
> buffer length 38
> [Package] Contains 1 Elements:
> [String] Length 00 = ""
>
>
> I found that the VBTx are addresses setup in the following file.
>
> src/vendorcode/google/chromeos/acpi/gnvs.asl:
>
> VBT0, 32, // 0x000 - Boot Reason
> VBT1, 32, // 0x004 - Active Main Firmware
> VBT2, 32, // 0x008 - Active EC Firmware
> VBT3, 16, // 0x00c - CHSW
> VBT4, 2048, // 0x00e - HWID
> VBT5, 512, // 0x10e - FWID
> VBT6, 512, // 0x14e - FRID
> VBT7, 32, // 0x18e - active main firmware type
> VBT8, 32, // 0x192 - Recovery Reason
> VBT9, 32, // 0x196 - FMAP base address
> CHVD, 24576, // 0x19a - VDAT space filled by verified boot
> VBTA, 32, // 0xd9a - pointer to smbios FWID
> MEHH, 256, // 0xd9e - Management Engine Hash
> RMOB, 32, // 0xdbe - RAM oops base address
> RMOL, 32, // 0xdc2 - RAM oops length
> ROVP, 32, // 0xdc6 - pointer to RO_VPD
> ROVL, 32, // 0xdca - size of RO_VPD
> RWVP, 32, // 0xdce - pointer to RW_VPD
> RWVL, 32, // 0xdd2 - size of RW_VPD
> // 0xdd6
>
> Can I assume that the info I want is only accessible in runtime and
> is not
> exported via the static tables?
Yes. Basically these are pointing to a memory address. From user space
you can't read this memory. We are planing to do something for this,
but it will take sometime.
Thanks,
Srinivas
>
> Thanks,
> Enric
next prev parent reply other threads:[~2020-03-25 22:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 9:43 [PATCH v2] platform: x86: Add ACPI driver for ChromeOS Enric Balletbo i Serra
2020-03-22 11:10 ` Greg Kroah-Hartman
2020-03-24 16:31 ` Enric Balletbo i Serra
2020-03-24 16:49 ` Greg Kroah-Hartman
2020-03-24 17:08 ` Enric Balletbo i Serra
2020-03-24 17:16 ` Greg Kroah-Hartman
2020-03-24 17:20 ` Srinivas Pandruvada
2020-03-25 20:34 ` Enric Balletbo i Serra
2020-03-25 21:41 ` Srinivas Pandruvada
2020-03-25 21:54 ` Enric Balletbo i Serra
2020-03-25 22:38 ` Srinivas Pandruvada [this message]
2020-03-22 15:21 ` Srinivas Pandruvada
2020-03-24 16:36 ` Enric Balletbo i Serra
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=6f90d8fa0301b19ddae3e7558df6408e23f4e04b.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=2pi@mok.nu \
--cc=andy@infradead.org \
--cc=ayman.bagabas@gmail.com \
--cc=bleung@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=dtor@chromium.org \
--cc=dvhart@infradead.org \
--cc=enric.balletbo@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=gwendal@chromium.org \
--cc=jekhor@gmail.com \
--cc=jeremy@system76.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajatja@google.com \
--cc=vbendeb@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).