On Thu, Jan 12, 2017 at 04:53:32PM +0200, Евгени Димитров wrote:
On Thu, Jan 12, 2017 at 4:45 PM, Kevin O'Connor kevin@koconnor.net wrote:
The additional debugging reports the controller is running and not reporting an error (which is in addition to the transfer descriptor reporting that it is also running without error). I'm not sure what is going on. Can you try disabling CONFIG_MALLOC_UPPERMEMORY and retry?
That did it. Do you think it's safe to just leave this option off?
Yes, it's safe. Some chipsets wont do DMA to the memory region between 0xc0000-0x100000. It looks like you have one of those boards. This can also be specified in the coreboot build - see src/mainboard/intel/mohonpeak/config_seabios and src/mainboard/intel/mohonpeak/Kconfig for an example of how to do that.
-Kevin
On Thursday, January 12, 2017, Kevin O'Connor kevin@koconnor.net wrote:
On Thu, Jan 12, 2017 at 04:53:32PM +0200, Евгени Димитров wrote:
On Thu, Jan 12, 2017 at 4:45 PM, Kevin O'Connor kevin@koconnor.net
wrote:
The additional debugging reports the controller is running and not reporting an error (which is in addition to the transfer descriptor reporting that it is also running without error). I'm not sure what is going on. Can you try disabling CONFIG_MALLOC_UPPERMEMORY and retry?
That did it. Do you think it's safe to just leave this option off?
Yes, it's safe. Some chipsets wont do DMA to the memory region between 0xc0000-0x100000. It looks like you have one of those boards. This can also be specified in the coreboot build - see src/mainboard/intel/mohonpeak/config_seabios and src/mainboard/intel/mohonpeak/Kconfig for an example of how to do that.
-Kevin
Thank you very much :)