From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen Kernel (3.0.2) breaks b44 module Date: Fri, 12 May 2006 10:03:55 +0100 Message-ID: References: <00a801c67599$bfc2ab50$fe02420a@BDR529> <44646A15.76E4.0078.0@novell.com> 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: <44646A15.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: xen@wood.id.au, xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 12 May 2006, at 09:57, Jan Beulich wrote: > This ought to be attributed to the fact that B44 supports only 30-bit > DMA addresses (and does special checking), but > XenLinux doesn't have a distinct DMA zone restricted to 24-bit > addresses, and both dma_alloc_coherent() and swiotlb are > restricting physical addresses to 31 bits only (at least the former > could certainly look at the device's DMA mask and > use that value rather than hard-coding 31). If dma_alloc_coherent isn't doing that then it should be patched to do so. Even though it won't help right now (since Xen will reject any requests more restricted than 31 bits) it will be needed when Xen is fixed to support basket-case hardware. -- Keir