Age | Commit message (Collapse) | Author |
|
To maintain the initialization state of the timestamp facility, the
pointer to the CBMEM section containing the timestamp table should be
kept in the .data section (so that it is maintained across u-boot
relocation).
BUG=chromium-os:20733
TEST=manual
. build a new firmware image
. program it on a Stumpy configured for ssh communications
. reboot the stumpy
. examine the timestamp log
(host) ssh <target ip addr> /var/cbmem.py| grep -A1 'time base'
time base 2195144, total entries 4
1:77,700 2:767,214 1000:1,409,204 1100:2,274,851
observe the new timestamp entry added to the log.
Change-Id: I71edb31f1c0c7b3d24dcc9a611efc999615e09d2
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/10003
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
|
|
A few CBMEM table entries are included in coreboot to let u-boot
discover the locations of those entries. They all are passed
using the same structure within coreboot table. This patch makes
use of that structure for all communicated entries (timestam,
console and MRC cache).
It does not make sense to keep types of pointers in the sysinfo
table, as nobody but the respective users of those fields use the
types. Let's keep the pointers as void *, this also allows to
reduce the amount of include files in systinfo.h and hide the
timestamp structures in timestamp.c.
BUG=chrome-os-partner:4200
TEST=manual
. build the new firmware and program it on a stumpy
. restart the machine
. after it comes up to ChromeOS, run the cbmem.py utility
Observe that timstamp values are displayed, and there is an entry
with index 1000 (added by u-boot to the coreboot timestamp
table).
Change-Id: Icb808145c4c62cee939eceb3d5bf5afb3bcd00d9
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/8711
Reviewed-by: Stefan Reinauer <reinauer@google.com>
|
|
This change turns on the code which allows u-boot to add
timestamps to the timestamp table created by coreboot.
Since u-boot does not use the tsc_t like structure to represent
HW counter readings, this structure is being replaced by 64 bit
integer.
The timestamp_init() function is now initializing the base timer
value used by u-boot to calculate the HW counter increments.
Timestamp facility is initialized as soon as the timestamp table
pointer is found in the coreboot table. The u-boot generated
timer events' ID will start at 1000 to clearly separate u-boot
events from coreboot events in the timer trace.
BUG=chromium-os:20733
TEST=manual
A Python script was used to retrieve the CBMEM timestamp table
while running CromeOS. The script will later be submitted into
the ChromeOS tools directory.
The following output was generated by the script:
localhost ~ # /var/vbendeb/cbmem.py
id 1, value 804,824,023
id 2, value 7,846,816,530
id 1000, value 19,356,528,758
Change-Id: I48c46e7b5cd2b2601d12465e0d8946152f31126e
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/8274
Reviewed-by: Stefan Reinauer <reinauer@google.com>
|
|
This change adds code to process the timestamp table infiormation
in case it is included in the coreboot table.
coreboot/timestamp.h had to be modified to make it possible to
compile in u-boot environment. The upcoming change will modify
the timestamp handling code borrowed from coreboot under
http://gerrit.chromium.org/gerrit/8164.
BUG=chromium-os:20733
TEST=manual
. brought up a stumpy to ChromeOS login screen.
Change-Id: I008b5e4c971cbb13de2f055f53da6384035df5eb
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/8222
Reviewed-by: Stefan Reinauer <reinauer@google.com>
Reviewed-by: Gabe Black <gabeblack@chromium.org>
|
|
This CL adds coreboot sources as is, they are not yet being
compiled and will have to be modified to get included in u-boot.
This is just a checkpoint checkin to establish a baseline for
future modifications.
BUG=chromium-os:20733
TEST=none
Change-Id: Ia2a8e108206b1dd7c27d72e5c72e35b386c3b151
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/8164
Reviewed-by: Stefan Reinauer <reinauer@chromium.org>
|