[coreboot] What problems are there with native RAM initialization on Intel Sandy Bridge?

Matt DeVillier matt.devillier at gmail.com
Mon Sep 26 19:12:11 CEST 2016

Hi Paul,

I received feedback from a couple of users of my Stumpy firmware that they
thought it had bricked the machine, only to realize it wasn't bricked when
the either removed one of the sodimms or swapped out the factory modules
for another pair.  I wanted to compare results with the MRC blob vs native
raminit, which is what led me to finding the compilation issue with the
former.  I don't yet have any feedback on whether the MRC init worked
better for these users, just that the native was problematic


On Sun, Sep 25, 2016 at 10:33 AM, Paul Menzel <
paulepanter at users.sourceforge.net> wrote:

> Dear Matt,
> You commented in [1], that there are problems with native RAM
> initialization on Intel Sandy Bridge.
> > using native raminit seems to be problematic on several
> > samsung/stumpy devices, hence the use of the MRC blob instead
> In #coreboot, I was asked which ones there are. Could you please report
> those here, or in the bug tracker [2].
> Thanks,
> Paul
> [1] https://review.coreboot.org/16735/
> [2] https://ticket.coreboot.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20160926/bbd41b2d/attachment.html>

More information about the coreboot mailing list