Vadim Bendebury ae632fa21e cr50: add a function to tell between prod and dev keys
To keep things simple it has been decided to use a certain key ID bit
as an indication of a prod versus dev key type.

The key ID value is derived from the key value, and is easy to enforce
(by generating another key in case the value does not match the
required key type).

This information will also be available through the cr50 userspace
tool.

BRANCH=none
BUG=chrome-os-partner:58230
TEST=ran the new code on prod and dev devices; On prod:
   > sysinfo
   Reset flags: 0x00000800 (hard)
   Chip:        g cr50 B2
   RO keyid:    0x3716ee6b(dev)
   RW keyid:    0xb93d6539(dev)
   DEV_ID:      0x015bb2a9 0x04656742

    on dev:
   > sysinfo
   Reset flags: 0x00000800 (hard)
   Chip:        g cr50 B2
   RO keyid:    0xaa66150f(prod)
   RW keyid:    0xde88588d(prod)
   DEV_ID:      0x0180305d 0x04656742

Change-Id: I37b12e02eb62f4f86bb58468ee301e77446451da
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/410291
Reviewed-by: Bill Richardson <wfrichar@chromium.org>
2016-11-15 17:42:44 -08:00
2016-11-15 17:41:53 -08:00
2016-11-10 21:28:33 -08:00
2016-09-09 19:20:12 -07:00
2012-05-11 09:11:52 -07:00
2016-10-14 16:05:49 -07:00
2016-10-14 16:05:49 -07:00
2014-04-02 19:58:53 +00:00
2015-12-08 20:05:05 -08:00

For an overview of the Embedded Controller firmware, refer to

http://www.chromium.org/chromium-os/2014-firmware-summit

For instructions on building from source, refer to

http://www.chromium.org/chromium-os/ec-development/getting-started-building-ec-images-quickly
Description
No description provided
Readme 1.4 GiB
Languages
C 64.7%
Lasso 20.7%
ASL 3.6%
JavaScript 3.2%
C# 2.9%
Other 4.6%