On Tue, Mar 20, 2012 at 10:50 PM, Subash Patel <subashrp@xxxxxxxxx> wrote: > Sorry for digging this very late. But as part of integrating dma_map v7 & > sysmmu v12 on 3.3-rc5, I am facing below issue: > > a) By un-selecting IOMMU in menu config, I am able to allocate memory in > vb2-dma-contig > > b) When I enable SYSMMU support for the IP's, I am receiving below fault: > > Unhandled fault: external abort on non-linefetch (0x818) at 0xb6f55000 > > I think this has something to do with the access to the SYSMMU registers for > writing the page table. Has anyone of you faced this issue while testing > these(dma_map+iommu) patches on kernel mentioned above? This must be > something related to recent changes, as I didn't have issues with these > patches on 3.2 kernel. > 0xb6f55000 is not an address of SYSMMU register if your kernel starts at 0xc0000000. Can you tell me any detailed information or situation? Regards, KyongHo. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |