We are using coreboot 4.4 only, because when I do dmidecode – t 0, its showing me bios version as 4.4-573.
Still type 17 doesn’t come up. How we can access DIMM information from HOB? From: cheng yichen [mailto:blessyic...@gmail.com] Sent: 25 January 2017 15:35 To: Mayuri Tendulkar <mayuri.tendul...@aricent.com> Cc: David Hendricks <dhend...@google.com>; coreboot <coreboot@coreboot.org> Subject: Re: [coreboot] SMBIOS table enablement in coreboot Hi Mayuri I have the same question with braswell coreboot that the source code is got from intel. Intel source code don't implement smbios type 17. but you can get dimm information in HOB that is created in FSB image. If you use coreboot4.4 for your bay trail platform. I think the type 17 is created. Thank you 2017-01-25 17:48 GMT+08:00 Mayuri Tendulkar <mayuri.tendul...@aricent.com<mailto:mayuri.tendul...@aricent.com>>: Hi David Thanks for response. So are there any other settings which enable Type 17 i.e. DDR data information in SMBIOS? We don’t see this Type 17 information in our table. Regards Mayuri From: David Hendricks [mailto:dhend...@google.com<mailto:dhend...@google.com>] Sent: 18 January 2017 01:58 To: Mayuri Tendulkar <mayuri.tendul...@aricent.com<mailto:mayuri.tendul...@aricent.com>> Cc: coreboot <coreboot@coreboot.org<mailto:coreboot@coreboot.org>> Subject: Re: [coreboot] SMBIOS table enablement in coreboot Hi Mayuri, On Sun, Jan 15, 2017 at 5:40 PM, Mayuri Tendulkar <mayuri.tendul...@aricent.com<mailto:mayuri.tendul...@aricent.com>> wrote: Hi David Yes, below are settings for our system. As we are using Intel Baytrail, does this SMBIOS manufacturer shd be Intel? That's up to you. Mainboard manufacturer, along with product name, serial number, and version, are strings which are expected to be assigned by the vendor. You may set these in your mainboard's Kconfig file. The Macbook 2.1 port shows an example of how to do this: https://review.coreboot.org/cgit/coreboot.git/tree/src/mainboard/apple/macbook21/Kconfig#n32. Other SMBIOS tables such as memory info is generated automatically by coreboot. For example, the type 4 table should have details about your processor manufacturer (Intel) as well as information which implies Baytrail (CPU family, model, and stepping). CONFIG_MAINBOARD_SMBIOS_MANUFACTURER="xxxxx" # CONFIG_SMBIOS_PROVIDED_BY_MOBO is not set CONFIG_GENERATE_SMBIOS_TABLES=y CONFIG_MAINBOARD_SMBIOS_PRODUCT_NAME="yyyy" Regards Mayuri From: David Hendricks [mailto:dhend...@google.com<mailto:dhend...@google.com>] Sent: 14 January 2017 08:19 To: Mayuri Tendulkar <mayuri.tendul...@aricent.com<mailto:mayuri.tendul...@aricent.com>> Cc: coreboot <coreboot@coreboot.org<mailto:coreboot@coreboot.org>> Subject: Re: [coreboot] SMBIOS table enablement in coreboot Hi Mayuri, Do you have GENERATE_SMBIOS_TABLES enabled in your config? On Fri, Jan 13, 2017 at 12:56 AM, Mayuri Tendulkar <mayuri.tendul...@aricent.com<mailto:mayuri.tendul...@aricent.com>> wrote: Hi We are using coreboot for our board based on Intel Baytrail 3845. When we use dmidecode –t to get DDR details, we get empty. It means data is missing in SMBIOS. Are there any settings in coreboot to enable this? Regards Mayuri "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." -- coreboot mailing list: coreboot@coreboot.org<mailto:coreboot@coreboot.org> https://www.coreboot.org/mailman/listinfo/coreboot -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc. "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." -- David Hendricks (dhendrix) Systems Software Engineer, Google Inc. "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." -- coreboot mailing list: coreboot@coreboot.org<mailto:coreboot@coreboot.org> https://www.coreboot.org/mailman/listinfo/coreboot "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
-- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
