Date: Mon, 8 Mar 2004 21:55:41 -0700
From: Deepak Saxena <dsaxena@plexity.net>
To: linux-kernel@vger.kernel.org
Subject: Re: pci_set_dma_mask()/pci_dma_supported() & broken PCI bridge issue
Message-ID: <20040309045541.GA9718@plexity.net>
Reply-To: dsaxena@plexity.net
References: <20040309044138.GA9491@plexity.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040309044138.GA9491@plexity.net>
User-Agent: Mutt/1.3.28i
Organization: Plexity Networks
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 807
Lines: 18

On Mar 08 2004, at 21:41, Deepak Saxena was caught saying:
> 
> I am a bit confused about the proper way that dma_set_mask() should
> behave. My situation is that I have an ARM core that has broken
> PCI window, allowing DMA only to/from the lower 64MB of RAM. My
> current approach to get around this is custom dma-API functions
> that trap based on (dev->bus == &pci_bus_type && *dev->dma_mask !=
> 0xfffffff). If dma_mask is 0xfffffff, I use the generic ARM dma API

I meant 0xffffffff

-- 
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/