TL;DR: If someone wants to deprecate older code then *they* have to
first balance any compatibility debt introduced by the newer code.
Anything else incentivises a race to the bottom; to move fast and
break things. coreboot IMO neither wants nor needs that.
Patrick Georgi via coreboot wrote:
>
Hi Angel,
I hope you're doing fine!
Thanks for your answer!
Ouch, hum, okay, understood...
So RAM init is more easy on already supported hardware?
What would be the effort to reach at least serialICE?
Thanks in advance,
Have a nice day,
Best Regards,
Mickaël.
Hi Pedro,
On Fri, Nov 26, 2021 at 11:02 PM Pedro Erencia wrote:
>
> Hi,
>
> I'm thinking about porting coreboot to a FM2A88X Extreme4+ board. This board
> has a DIP8 flash with a socket and I wondered what would be the best way to
> do an efficient development cycle. Ideally, I suppose that
you could end up "bricking" the motherboard.
>On Fri, Nov 26, 2021 at 3:02 PM Pedro Erencia wrote:
> Hi,
>
> I'm thinking about porting coreboot to a FM2A88X Extreme4+ board. This
> board has a DIP8 flash with a socket and I wondered what would be the best
> way to do an efficient development
Hi Pedro,
On 27.11.21 00:02, Pedro Erencia wrote:
> I'm thinking about porting coreboot to a FM2A88X Extreme4+ board. This
> board has a DIP8 flash with a socket and I wondered what would be the best
> way to do an efficient development cycle. Ideally, I suppose that the best
> option would be to
5 matches
Mail list logo
