From e1a4127c93754e2f4697900d37e6979a03be1920 Mon Sep 17 00:00:00 2001 From: Erik Hovland Date: Wed, 22 Mar 2006 21:02:11 +0000 Subject: [PATCH] --- yaml --- r: 22859 b: refs/heads/master c: 3a2916aa289504d694072a98876d23ca31d6401e h: refs/heads/master i: 22857: f1da56ec08bf377dd28f02e9d3ea6ae8895d1237 22855: 8ab6a43891a8de5272781cdab039011015300fe3 v: v3 --- [refs] | 2 +- trunk/arch/arm/common/dmabounce.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index a0cc0139e230..f9d0c352292e 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 69b648a200b27a7c8ea92993bf5b4d40e83b5403 +refs/heads/master: 3a2916aa289504d694072a98876d23ca31d6401e diff --git a/trunk/arch/arm/common/dmabounce.c b/trunk/arch/arm/common/dmabounce.c index ad6c89a555bb..7971d0dc6892 100644 --- a/trunk/arch/arm/common/dmabounce.c +++ b/trunk/arch/arm/common/dmabounce.c @@ -5,7 +5,7 @@ * limited DMA windows. These functions utilize bounce buffers to * copy data to/from buffers located outside the DMA region. This * only works for systems in which DMA memory is at the bottom of - * RAM and the remainder of memory is at the top an the DMA memory + * RAM, the remainder of memory is at the top and the DMA memory * can be marked as ZONE_DMA. Anything beyond that such as discontigous * DMA windows will require custom implementations that reserve memory * areas at early bootup.