From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: IVTV and Xen Date: Mon, 1 May 2006 07:45:35 +0100 Message-ID: <3ac635b4dd93e7696042238ab96f940b@cl.cam.ac.uk> References: <44559A93.7050504@q3aiml.net> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <44559A93.7050504@q3aiml.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andy Clayton Cc: Jason , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 1 May 2006, at 06:20, Andy Clayton wrote: >> Has anyone had any luck getting IVTV .61 working in xen (Im on 3.0 >> unstable changeset Fri Mar 31 >> 00:26:07 2006 +0100 9494:8a8361994904 because of some unrelated >> driver issues with another device). >> I keep getting a DMA issue. If this is fixed in a later rev, I will >> upgrade but that will be a >> pretty major undertaking on this particular machine, so I thought I >> would ask for others experience >> first. This is what I get when the module inserts, this ia DomU >> kernel BTW. >> > It has been a while, but I think I had a similar error with ivtv that > could be fixed by passing "swiotlb=force" to the kernel (extra in the > configs). This was with an unstable changeset in between 3.0.1 and > 3.0.2. We've never enabled swiotlb by default for domUs, even when they're driver domains. So you will definitely need 'swiotlb=force'. You could try 'swiotlb=16,force' for a 16MB swiotlb (the default is 64MB which may burn an unnecessary amount of RAM). -- Keir