[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090507201538U.fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 7 May 2009 20:14:48 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: mingo@...e.hu
Cc: fujita.tomonori@....ntt.co.jp, airlied@...ux.ie,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
mingo@...hat.com, dwmw2@...radead.org
Subject: Re: IOMMU and graphics cards
On Thu, 7 May 2009 13:01:35 +0200
Ingo Molnar <mingo@...e.hu> wrote:
>
> * FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:
>
> > > The proprietary drivers make problems so far. For the ATI one I
> > > am in contact with the developers to try to fix it. But I can't
> > > do anything about the other proprietary driver I am aware of :-(
> >
> > I don't know anything about the graphic drivers but are there any
> > other proprietary drivers except for ATI and AMD? Fixing only two
> > drivers to make the majority happy?
>
> ATI ~== AMD these days. The problem is Nvidia cards stuck into AMD
> systems.
Oops, I meant ATI and Nvidia.
> I guess refusing those DMA accesses (and printing something
> meaningful and relentlessly honest so that the user knows where the
> problem comes from) is the proper solution.
Refusing DMA means that we will break these broken drivers. That's
what David and I like. Yeah, telling users explicitly who is to blame
for the problem is even better.
> There will be some
> end-user moaning, there might be distros turning off the IOMMU code
> summarily, but nvidia-in-AMD-box is an unfriendly alliance to begin
> with.
--
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