summaryrefslogtreecommitdiffstats
path: root/arch/um/drivers/chan_kern.c
diff options
context:
space:
mode:
authorFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>2010-05-09 19:39:05 +0200
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>2010-05-21 09:31:13 +0200
commit99ec28f183daa450faa7bdad6f932364ae325648 (patch)
tree4fd2d505dd71412f2fc630ac700fc9a7348aaaab /arch/um/drivers/chan_kern.c
parentpowerpc: Build-in e1000e for pseries & ppc64_defconfig (diff)
downloadlinux-99ec28f183daa450faa7bdad6f932364ae325648.tar.xz
linux-99ec28f183daa450faa7bdad6f932364ae325648.zip
powerpc: Remove unused 'protect4gb' boot parameter
'protect4gb' boot parameter was introduced to avoid allocating dma space acrossing 4GB boundary in 2007 (the commit 569975591c5530fdc9c7a3c45122e5e46f075a74). In 2008, the IOMMU was fixed to use the boundary_mask parameter per device properly. So 'protect4gb' workaround was removed (the 383af9525bb27f927511874f6306247ec13f1c28). But somehow I messed the 'protect4gb' boot parameter that was used to enable the workaround. Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/um/drivers/chan_kern.c')
0 files changed, 0 insertions, 0 deletions