How about just changing the die() into a printk(BIOS_ALERT, ...) and an
assert(0)? Then people could use CONFIG_FATAL_ASSERTS to select whether
they would rather fail fast or try to keep booting as far as possible.
On Fri, Feb 24, 2017 at 7:46 AM, ron minnich wrote:
> For those of us working on
For those of us working on boards that don't ship in a product, the die()
is probably not appropriate. But if you intend to ship a real product then
you definitely want to die() if someone tries to use a CPU that's not
tested on the board.
Or at least that's the way it seems to me.
On Fri, Feb 2
On Fri, Feb 24, 2017 at 5:04 AM, wrote:
> Yes, this die() is what i mean. Try to get maybe some functionality is i
> think better then just stopping there and providing zero functionality.
>
> I also know, that there is a message when the CPUID is not known. Its about
> the die() afterwards.
Pat
Yes, this die() is what i mean. Try to get maybe some functionality is i think
better then just stopping there and providing zero functionality.
I also know, that there is a message when the CPUID is not known. Its about the
die() afterwards.
23. Feb 2017 14:31 by coreboot@coreboot.org:
> On
On Thu, Feb 23, 2017 at 2:39 AM, Nico Huber wrote:
> On 23.02.2017 00:07, i1w5d7gf38...@tutanota.com wrote:
>
>> There is a Filter to stop booting when the CPUID is not in a list of
>> supported CPUs. This filter does not make sense in the real world usage.
>
> It's not a filter. It's a measure to
On 23.02.2017 00:07, i1w5d7gf38...@tutanota.com wrote:
> There is a Filter to stop booting when the CPUID is not in a list of
> supported CPUs. This filter does not make sense in the real world usage.
It's not a filter. It's a measure to know which code to run for which
CPU. Please dig a little d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/2017 05:49 PM, i1w5d7gf38...@tutanota.com wrote:
> Thanks for the information. Then maybe just dont stop booting when
> CPUID is missing. Just add a line to the coreboot log. Something like:
> "WARNING: Unknown CPU ID detected. Please report
Thanks for the information. Then maybe just dont stop booting when CPUID is
missing. Just add a line to the coreboot log. Something like: "WARNING: Unknown
CPU ID detected. Please report to the coreboot mailing lists if the machine is
working fine"
Then you still have the same functionality as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/2017 05:31 PM, i1w5d7gf38...@tutanota.com wrote:
> What is the benefit of such a list? I cant see any benefit. Its only
> additional work that is useless.
Example: Certain CPUs require special cache handling / setup to avoid
unusual faults o
What is the benefit of such a list? I cant see any benefit. Its only additional
work that is useless.
A example for CPUID-List blocking functionality is commit
I63d308477a22a9e55ceed1b6b36e63a3044c2354
22. Feb 2017 23:15 by tpear...@raptorengineering.com:
> -BEGIN PGP SIGNED MESSAGE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/22/2017 05:07 PM, i1w5d7gf38...@tutanota.com wrote:
> There is a Filter to stop booting when the CPUID is not in a list of
> supported CPUs. This filter does not make sense in the real world usage.
> For example socket 775:
> When you enter a wo
There is a Filter to stop booting when the CPUID is not in a list of supported
CPUs. This filter does not make sense in the real world usage.
For example socket 775:
When you enter a working cpu, then it boots. In some cases the coreboot code
didnt work with a CPU where it should. For example so
12 matches
Mail list logo
