[coreboot] Query regarding CoreBoot

2020-06-08 Thread lol
Hi, I wanted to ask if coreboot is capable of booting macOS. There are
bootloaders like clover and opencore that does the job but does coreboot do
this thing with more efficiency?
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org


Re: [coreboot] Query regarding coreboot for new intel customized board

2016-05-26 Thread Zoran Stojsavljevic
Hello Mayuri,

You need to play (maybe, just a kludge) a bit with Coreboot "make
menuconfig", and there with console setup:

[image: Inline image 1]

You also might want to install on your Linux distro PuTTY console (given
UBUNTU apt-get and Fedora dnf commands), to set your Rx terminal correctly
(at least, I know PuTTY well, always worked for me):

sudo apt-get/dnf install putty

Zoran

On Thu, May 26, 2016 at 6:33 AM, Mayuri Tendulkar <
mayuri.tendul...@aricent.com> wrote:

> Thanks Vim.
>
>
>
> Currently I am not able to get any serial prints out on my reference board.
>
>
>
> My board is based on Intel ISX board based on Baytrail-I soc E3825 given
> below.
>
>
>
>
> https://www-ssl.intel.com/content/www/us/en/embedded/design-tools/evaluation-platforms/atom-e3800-dev-kit-isx-ref-design-product-brief.html
>
>
>
> I have built coreboot for this, but unable to get serial prints.
>
>
>
> How I should debug this further.
>
>
>
> Regards
>
> Mayuri
>
>
>
> *From:* Wim Vervoorn [mailto:wvervo...@eltan.com]
> *Sent:* 24 May 2016 13:26
> *To:* Mayuri Tendulkar <mayuri.tendul...@aricent.com>
> *Subject:* Re: Query regarding coreboot for new intel customized board
>
>
>
> Hello Mayuri,
>
>
>
> If your rom image is the same it could be due to the lack of support for
> the flash device you are using. The MRC cache is preserved in flash so you
> need to be able to write it.
>
>
>
> For the others the numbers etc you mention are informational for the OS.
> They are not strictly required but the OS builds a registry of the items it
> retrieves from the SMBIOS. If you don’t require this you could also disable
> the functionality.
>
>
>
>
>
> Best Regards,
>
> Wim Vervoorn
>
>
>
> Eltan B.V.
>
> Ambachtstraat 23
>
> 5481 SM Schijndel
>
> The Netherlands
>
>
>
> T : +31-(0)73-594 46 64
>
> E : wvervo...@eltan.com
>
> W : http://www.eltan.com
>
> "THIS MESSAGE CONTAINS CONFIDENTIAL INFORMATION. UNLESS YOU ARE THE
> INTENDED RECIPIENT OF THIS MESSAGE, ANY USE OF THIS MESSAGE IS STRICTLY
> PROHIBITED. IF YOU HAVE RECEIVED THIS MESSAGE IN ERROR, PLEASE IMMEDIATELY
> NOTIFY THE SENDER BY TELEPHONE +31-(0)73-5944664 OR REPLY EMAIL, AND
> IMMEDIATELY DELETE THIS MESSAGE AND ALL COPIES."
>
>
>
>
>
>
>
>
>
>
>
> *From:* coreboot [mailto:coreboot-boun...@coreboot.org
> <coreboot-boun...@coreboot.org>] *On Behalf Of *Mayuri Tendulkar
> *Sent:* Tuesday, May 24, 2016 7:26 AM
> *To:* coreboot <coreboot@coreboot.org>
> *Subject:* [coreboot] Query regarding coreboot for new intel customized
> board
>
>
>
> Hi team
>
>
>
> I am working on building coreboot for one of our customized board. This is
> based on Intel ISX board reference design, reference can be taken as
> Minnowboard or BayleyBay CRB.
>
>
>
> As per documentation given under coreboot, I created folder with my board
> name under src/intel/mainboard/xxx and did changes required.
>
>
>
> If I tried the coreboot with these changes on minnowboard, it got stuck at
> FSP MRC Cache not found.
>
>
>
> But if the same code changes I copied under  src/intel/mainboard/minnowmax
> and built, it booted fine.
>
>
>
> I would like to know what is the importance of these board names, SMBIOS
> table name, serial no which are defined for Minnowmax.
>
>
>
> Is there some master registry where all these are stored, and if any new
> entry comes, how we should add it.
>
>
>
> 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."
> "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
>
-- 
coreboot mailing list: coreboot@coreboot.org
https://www.coreboot.org/mailman/listinfo/coreboot

Re: [coreboot] Query regarding coreboot for new intel customized board

2016-05-25 Thread Naveed Ghori
That looks a lot like the Valley Island design.

I was able to get serial output by overwriting coreboot (last 2MB of the 8MB 
bios chip) on the bios that comes with it.
However as you will see in the history of emails still get stuck during the 
boot process.

Hope the above helps you get further.

From: coreboot [mailto:coreboot-boun...@coreboot.org] On Behalf Of Mayuri 
Tendulkar
Sent: Thursday, 26 May 2016 12:33 PM
To: Wim Vervoorn; coreboot
Subject: Re: [coreboot] Query regarding coreboot for new intel customized board

Thanks Vim.

Currently I am not able to get any serial prints out on my reference board.

My board is based on Intel ISX board based on Baytrail-I soc E3825 given below.

https://www-ssl.intel.com/content/www/us/en/embedded/design-tools/evaluation-platforms/atom-e3800-dev-kit-isx-ref-design-product-brief.html

I have built coreboot for this, but unable to get serial prints.

How I should debug this further.

Regards
Mayuri

From: Wim Vervoorn [mailto:wvervo...@eltan.com]
Sent: 24 May 2016 13:26
To: Mayuri Tendulkar 
<mayuri.tendul...@aricent.com<mailto:mayuri.tendul...@aricent.com>>
Subject: Re: Query regarding coreboot for new intel customized board

Hello Mayuri,

If your rom image is the same it could be due to the lack of support for the 
flash device you are using. The MRC cache is preserved in flash so you need to 
be able to write it.

For the others the numbers etc you mention are informational for the OS. They 
are not strictly required but the OS builds a registry of the items it 
retrieves from the SMBIOS. If you don't require this you could also disable the 
functionality.


Best Regards,
Wim Vervoorn

Eltan B.V.
Ambachtstraat 23
5481 SM Schijndel
The Netherlands

T : +31-(0)73-594 46 64
E : wvervo...@eltan.com<mailto:wvervo...@eltan.com>
W : http://www.eltan.com
"THIS MESSAGE CONTAINS CONFIDENTIAL INFORMATION. UNLESS YOU ARE THE INTENDED 
RECIPIENT OF THIS MESSAGE, ANY USE OF THIS MESSAGE IS STRICTLY PROHIBITED. IF 
YOU HAVE RECEIVED THIS MESSAGE IN ERROR, PLEASE IMMEDIATELY NOTIFY THE SENDER 
BY TELEPHONE +31-(0)73-5944664 OR REPLY EMAIL, AND IMMEDIATELY DELETE THIS 
MESSAGE AND ALL COPIES."





From: coreboot [mailto:coreboot-boun...@coreboot.org] On Behalf Of Mayuri 
Tendulkar
Sent: Tuesday, May 24, 2016 7:26 AM
To: coreboot <coreboot@coreboot.org<mailto:coreboot@coreboot.org>>
Subject: [coreboot] Query regarding coreboot for new intel customized board

Hi team

I am working on building coreboot for one of our customized board. This is 
based on Intel ISX board reference design, reference can be taken as 
Minnowboard or BayleyBay CRB.

As per documentation given under coreboot, I created folder with my board name 
under src/intel/mainboard/xxx and did changes required.

If I tried the coreboot with these changes on minnowboard, it got stuck at FSP 
MRC Cache not found.

But if the same code changes I copied under  src/intel/mainboard/minnowmax and 
built, it booted fine.

I would like to know what is the importance of these board names, SMBIOS table 
name, serial no which are defined for Minnowmax.

Is there some master registry where all these are stored, and if any new entry 
comes, how we should add it.

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."
"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

[coreboot] Query regarding coreboot for new intel customized board

2016-05-23 Thread Mayuri Tendulkar
Hi team

I am working on building coreboot for one of our customized board. This is 
based on Intel ISX board reference design, reference can be taken as 
Minnowboard or BayleyBay CRB.

As per documentation given under coreboot, I created folder with my board name 
under src/intel/mainboard/xxx and did changes required.

If I tried the coreboot with these changes on minnowboard, it got stuck at FSP 
MRC Cache not found.

But if the same code changes I copied under  src/intel/mainboard/minnowmax and 
built, it booted fine.

I would like to know what is the importance of these board names, SMBIOS table 
name, serial no which are defined for Minnowmax.

Is there some master registry where all these are stored, and if any new entry 
comes, how we should add it.

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
https://www.coreboot.org/mailman/listinfo/coreboot