[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081020123245J.fujita.tomonori@lab.ntt.co.jp>
Date: Mon, 20 Oct 2008 12:32:43 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: joro@...tes.org
Cc: dwmw2@...radead.org, mingo@...e.hu,
iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
fenghua.yu@...el.com, tony.luck@...el.com,
suresh.b.siddha@...el.com, sfr@...b.auug.org.au,
andreas.herrmann3@....com, joseph.cihula@...el.com,
akpm@...ux-foundation.org, jbarnes@...tuousgeek.org,
tglx@...utronix.de, torvalds@...ux-foundation.org
Subject: Re: [ANNOUNCE] iommu-2.6.git tree
On Sun, 19 Oct 2008 23:23:27 +0200
Joerg Roedel <joro@...tes.org> wrote:
> On Sun, Oct 19, 2008 at 02:21:14PM +0100, David Woodhouse wrote:
> > I thought you and Thomas were working together, and I spoke to Thomas
> > about it during the Kernel Summit. Unless I'm very much mistaken, he
> > agreed that it makes sense to have a separate, real, git tree for
> > cross-platform IOMMU-related work.
>
> Is there any cross-platform IOMMU-related work outside the Intel IOMMU
> development?
IA64 and PARISC uses the same IOMMU hardware but they duplicate the
driver for them (the drivers are very similar). Calgary and POWER also
have similar IOMMU drivers. But I don't think it's worth merging them.
Unless a new cross-platform IOMMU git tree handles DMA-API changes,
there is no point in having such new tree. There is very little
non-architecture-specific IOMMU stuff.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists