From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Clayton Subject: Re: IVTV and Xen Date: Mon, 01 May 2006 00:20:19 -0500 Message-ID: <44559A93.7050504@q3aiml.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jason Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Jason 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. When I changed over to 3.0.2 I believe it then started to panic with the setting, but booted fine without. Since I've been busy trying to get a FreeBSD domU to work and have it not panic every two seconds, I have yet to look into it further. Additionally when using that setting I could capture video initially, but after some time it would lock up. I don't know if that issue was related. Anyways it would seem as if something affecting the issue was changed in or around 3.0.2--assuming my memory is even partially correct. That setting may still be worth a try, though, if you do not want to try upgrading. Sorry for the continuous stream of guessing and I thinks---Hopefully it helps, Andy Clayton