> -----Original Message----- > From: Bao, Zheng [mailto:[email protected]] > Sent: Sunday, May 17, 2009 8:12 PM > To: Myles Watson; Patrick Georgi > Cc: coreboot > Subject: RE: [coreboot] [PATCH] Table code cleanup > > 1. We have disabled the display controller. How did you disable it? The message "uma_memory_start=...." shouldn't appear if CONFIG_GFXUMA == 0.
> 2. How is the region reserved? What can we do? Help us understand what the desired behavior is. I'm looking at dbm690t/mainboard.c wondering why uma_memory_size = 0x8000000; when CONFIG_GFXUMA == 0. It doesn't make too much sense to hard code the address there. > Sorry, I didn't trace the roadmap of HIGH_TABLE and have no idea about > what happened. I really need more help to solve this issue. HIGH TABLES just puts the ACPI tables in higher memory. It's not that bad, but there are a few kinks to be worked out. Something else I don't understand is why UMA allocation is saved until enable. Shouldn't it be done with resource allocation? It doesn't make sense to do it after the tables are written. Thanks, Myles -- coreboot mailing list: [email protected] http://www.coreboot.org/mailman/listinfo/coreboot
