| commit | 99ec28f183daa450faa7bdad6f932364ae325648 | |
| author | FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> | |
| Sun, 9 May 2010 17:39:05 +0000 (9 17:39 +0000) | ||
| committer | Benjamin Herrenschmidt <benh@kernel.crashing.org> | |
| Fri, 21 May 2010 07:31:13 +0000 (21 17:31 +1000) | ||
| tree | 4fd2d505dd71412f2fc630ac700fc9a7348aaaab | treesnapshot (tar.gz zip) |
| parent | 40a5a4435f37b172dec09852ad2036865f9ca3c8 | commitdiff |
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>
'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>
| arch/powerpc/kernel/iommu.c | diffblobblamehistory |