Hi there,
this is the coreboot mailinglist. Please use the flashrom mailinglist
(flash...@flashrom.org) for any questions about flashrom.
Felix
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to
> The word 'drop' has ominous connotations, but it's not a deletion. A board is
> never really gone.
"Dropping" 50 boards may be ominous in relation to the future of the
coreboot project:
1. These boards will be gone for the people who check the "mainboards
supported by coreboot" and see only
On November 25, 2021 4:43:35 PM UTC, Patrick Georgi via coreboot
wrote:
>On 25.11.21 17:04, Mike Banon wrote:
>These users didn't contribute fixes to their boards (or even just feedback
>that things needs to be done and testing when others provide patches) - are
>they even contributors?
>
Dear coreboot folks,
Am 25.11.21 um 17:43 schrieb Patrick Georgi:
On 25.11.21 17:04, Mike Banon wrote:
[…]
[ forking threat, and follow-up comment ]
Please let’s not escalate this. (Type your answer, save it in the draft
folder, sleep over it, and then think if you want to send it.)
I
> 1. These boards will be gone for the people who check the "mainboards
> supported by coreboot" and see only the "new Intel stuff". This
> hinders the coreboot community growth around the "gone boards", and
> also of the coreboot community in general: the fewer boards are
> supported by coreboot,
Am 25.11.2021 um 18:06 schrieb AreYouLoco? via coreboot:
In my opinion coreboot is more developer friendly than user friendly.
Kinda obvious: We don't even ship binaries...
Given the trouble these deprecation announcements always are, I can tell
you an even more developer friendly strategy:
> To address the OP, it seems like there is some activity on getting an
> AGESA RESOURCE_ALLOCATOR_V4 working, but is an AGESA PARALLEL_MP init
> also needed (and is there any activity or something I can do to help?)
> Realize resources may not exist to spoon feed problem definitions to a
> level
Patrick Georgi via coreboot:
On 25.11.21 17:04, Mike Banon wrote:
2. It's not just the loss of boards - it's also the loss of coreboot
users/contributors who only have these boards and don't want to switch
These users didn't contribute fixes to their boards (or even just
feedback that things
On 25.11.21 17:04, Mike Banon wrote:
2. It's not just the loss of boards - it's also the loss of coreboot
users/contributors who only have these boards and don't want to switch
These users didn't contribute fixes to their boards (or even just feedback that
things needs to be done and testing
It's definitely preferable to have platforms working in-tree rather than
out of tree. This is a *significant* portion of coreboot's supported
platforms and sends a strong signal to anyone using or considering them
that they can just forget about the coreboot project because the rug may be
pulled
I'm happy to contribute financially. It just comes with the caveat that
I need to know with some surety that I can finally have a working board
at the end of it.
On a side note is there any kind of crowd sourcing platform / escrow
service for GPL projects? I know it's been talked about, and
On Thu, Nov 25, 2021 at 9:50 PM Angel Pons wrote:
>
> TL;DR: The deprecation notice is a call for action. Please stop
> complaining about it, let's work on a solution instead. Especially
> when https://review.coreboot.org/q/topic:amd_resource_allocator_v4
> already exists, which implements some
Arthur Heymans:
https://review.coreboot.org/c/coreboot/+/48210 and
https://review.coreboot.org/c/coreboot/+/48262/ provided the implementation
for PARALLEL_MP on qemu.
Notice that modern AMD CPUs (soc/amd/¨*) also use PARALLEL_MP and can be
used as an example for AMD AGESA platforms too.
Good
> Do you remember from where you got these magic values? Suspect I'm going
> to need similar. Will investigate soc/amd/¨* too.
> /* QEMU-specific register */
> #define EXT_TSEG_MBYTES 0x50
> +#define SMRAMC 0x9d
> +#define C_BASE_SEG ((0 << 2) | (1 << 1) | (0 << 0))
> +#define G_SMRAME
Hi Mike,
I typically don't indulge in mailing list drama, but I'm sick and
tired of seeing people waste their time and energy along with others'.
This is not the first time I've seen something like this: something
similar happened about two years ago when other AMD boards (KGPE-D16
and KCMA-D8,
15 matches
Mail list logo
