From: Stefan Richter Date: Wed, 19 Dec 2007 16:33:05 +0000 Subject: Re: No dma_sync_* during pci_probe? (Sparc, post 2.6.22 regression) Message-Id: <476947C1.2010405@s5r6.in-berlin.de> List-Id: References: <47670BDF.80409@s5r6.in-berlin.de> <20071217.165032.41424988.davem@davemloft.net> <4767A323.7090205@s5r6.in-berlin.de> <20071218.142956.26529678.davem@davemloft.net> In-Reply-To: <20071218.142956.26529678.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Miller Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org, gregkh@suse.de, krh@bitplanet.net, linux1394-devel@lists.sourceforge.net David Miller wrote: > From: Stefan Richter > Date: Tue, 18 Dec 2007 11:38:27 +0100 > >> Also note: >> - The very same code did not oops at this point in 2.6.22. It only >> started doing so in 2.6.23. > > 2.6.23 is when the sparc64 IOMMU code started relying upon > the dev_archdata bits being correct. And why are the dev_archdata corrupt? Does arch/sparc64/kernel/pci.c fill them in incorrectly or too late? drivers/firewire/fw_ohci.c needs them for dma_map_single() + dma_sync_single_for_device() in the pci_driver.probe(), sometime after it called pci_enable_device(), before finishing the probe. -- Stefan Richter -===-=-== =-- =--= http://arcgraph.de/sr/