On 4/20/2015 8:51 AM, Aaron Durbin wrote:
On Fri, Apr 17, 2015 at 12:32 AM, Matt DeVillier matt.devillier@gmail.com wrote:
Greetings! When building upstream master tonight, discovered that cbmem console output is broken for Intel hardware (testing on google/panther). With some help on IRC from kmalkki, was able to determine the culprit is commit ec5e5e0 (New mechanism to define SRAM/memory map with automatic bounds checking). I verified this via bisecting; the prior commit, 06ef046, functions normally.
Did this get fixed?
not as of yet (cdf92ea still has the issue)
regards, Matt
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
On Mon, Apr 20, 2015 at 9:23 AM, Matt DeVillier matt.devillier@gmail.com wrote:
On 4/20/2015 8:51 AM, Aaron Durbin wrote:
On Fri, Apr 17, 2015 at 12:32 AM, Matt DeVillier matt.devillier@gmail.com wrote:
Greetings! When building upstream master tonight, discovered that cbmem console output is broken for Intel hardware (testing on google/panther). With some help on IRC from kmalkki, was able to determine the culprit is commit ec5e5e0 (New mechanism to define SRAM/memory map with automatic bounds checking). I verified this via bisecting; the prior commit, 06ef046, functions normally.
Did this get fixed?
not as of yet (cdf92ea still has the issue)
Try this if you have time? I'm sure I haven't handled all the cases, but it my work for you.
http://review.coreboot.org/#/c/9851/
regards, Matt
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot