ryu: Get rid of coreboot setting up DMA areas for libpayload

BUG=chrome-os-partner:31634
BRANCH=None
TEST=Compiles successfully and dma areas are setup fine by libpayload mmu

Change-Id: I1034a4dcf6c9ee56bee4ea5d18e91a8d51895429
Signed-off-by: Furquan Shaikh <furquan@google.com>
Reviewed-on: https://chromium-review.googlesource.com/217571
Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Tested-by: Furquan Shaikh <furquan@chromium.org>
Commit-Queue: Furquan Shaikh <furquan@chromium.org>
This commit is contained in:
Furquan Shaikh 2014-09-10 15:10:08 -07:00 committed by chrome-internal-fetch
commit 0425e87f21
2 changed files with 0 additions and 19 deletions

View file

@ -92,12 +92,4 @@ config EC_GOOGLE_CHROMEEC_I2C_BUS
hex
default 1
config DRAM_DMA_START
hex
default 0xc0000000
config DRAM_DMA_SIZE
hex
default 0x00200000
endif # BOARD_GOOGLE_RUSH_RYU

View file

@ -78,14 +78,3 @@ void mainboard_add_memory_ranges(struct memranges *map)
memranges_insert(map, CONFIG_DRAM_DMA_START, CONFIG_DRAM_DMA_SIZE,
MA_MEM | MA_MEM_NC | MA_NS | MA_RW);
}
void lb_board(struct lb_header *header)
{
struct lb_range *dma;
dma = (struct lb_range *)lb_new_record(header);
dma->tag = LB_TAB_DMA;
dma->size = sizeof(*dma);
dma->range_start = CONFIG_DRAM_DMA_START;
dma->range_size = CONFIG_DRAM_DMA_SIZE;
}