On Fri, Jul 26, 2013 at 6:28 AM, Cho KyongHo pullip@samsung.com wrote:
Signed-off-by: Cho KyongHo pullip@samsung.com
---
.../bindings/iommu/samsung,exynos4210-sysmmu.txt | 103 +++
arch/arm/boot/dts/exynos4.dtsi | 122
On Fri, Sep 27, 2013 at 09:00:01AM -0400, Will Deacon wrote:
Hi Andreas,
On Thu, Sep 26, 2013 at 11:36:19PM +0100, Andreas Herrmann wrote:
(Depending on DT information and module parameters) each device is put
into its own protection domain (if possible). For configuration with
one or
On Mon, 2013-10-07 at 05:46 +, Bhushan Bharat-R65777 wrote:
-Original Message-
From: Alex Williamson [mailto:alex.william...@redhat.com]
Sent: Friday, October 04, 2013 11:42 PM
To: Bhushan Bharat-R65777
Cc: j...@8bytes.org; b...@kernel.crashing.org;
Do you really want module dependencies between vfio and your core
kernel MSI setup? Look at the vfio external user interface that we've
already defined.
That allows other components of the kernel to get a proper reference
to a vfio group. From there you can work out how to get what
On Mon, 07 Oct 2013 08:44:54 -0500, Rob Herring wrote:
On Fri, Jul 26, 2013 at 6:28 AM, Cho KyongHo pullip@samsung.com wrote:
Signed-off-by: Cho KyongHo pullip@samsung.com
---
.../bindings/iommu/samsung,exynos4210-sysmmu.txt | 103 +++
arch/arm/boot/dts/exynos4.dtsi
