From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: David Miller <davem@davemloft.net>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@suse.de, krh@bitplanet.net,
linux1394-devel@lists.sourceforge.net
Subject: Re: No dma_sync_* during pci_probe? (Sparc, post 2.6.22 regression)
Date: Wed, 19 Dec 2007 17:33:05 +0100 [thread overview]
Message-ID: <476947C1.2010405@s5r6.in-berlin.de> (raw)
In-Reply-To: <20071218.142956.26529678.davem@davemloft.net>
David Miller wrote:
> From: Stefan Richter <stefanr@s5r6.in-berlin.de>
> 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/
next prev parent reply other threads:[~2007-12-19 16:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9160-4803@http.bugzilla.kernel.org/>
[not found] ` <47112797.7060003@s5r6.in-berlin.de>
2007-12-17 23:53 ` Stefan Richter
2007-12-18 0:50 ` David Miller
2007-12-18 10:38 ` Stefan Richter
2007-12-18 22:29 ` David Miller
2007-12-19 16:33 ` Stefan Richter [this message]
2007-12-19 23:06 ` David Miller
2007-12-20 8:40 ` David Miller
2007-12-20 20:19 ` Emanuele Rocca
2007-12-22 13:10 ` Stefan Richter
2007-12-18 22:30 ` David Miller
2007-12-19 21:08 ` Benjamin Herrenschmidt
2007-12-19 21:07 ` Benjamin Herrenschmidt
2007-12-18 2:58 ` Chris Newport
2007-12-18 3:03 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=476947C1.2010405@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=krh@bitplanet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®