From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 02 Aug 2007 13:51:38 +0100 (BST) Received: from h155.mvista.com ([63.81.120.155]:65169 "EHLO imap.sh.mvista.com") by ftp.linux-mips.org with ESMTP id S20022114AbXHBMvg (ORCPT ); Thu, 2 Aug 2007 13:51:36 +0100 Received: from [192.168.1.248] (unknown [10.150.0.9]) by imap.sh.mvista.com (Postfix) with ESMTP id 72EA83EC9; Thu, 2 Aug 2007 05:51:34 -0700 (PDT) Message-ID: <46B1D3CE.6070507@ru.mvista.com> Date: Thu, 02 Aug 2007 16:53:34 +0400 From: Sergei Shtylyov Organization: MontaVista Software Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803 X-Accept-Language: ru, en-us, en-gb MIME-Version: 1.0 To: "Maciej W. Rozycki" Cc: Ralf Baechle , linux-mips@linux-mips.org Subject: Re: Modpost warning on Alchemy References: <20070801115231.GA20323@linux-mips.org> <46B07B36.1000501@ru.mvista.com> <46B086EB.2030101@ru.mvista.com> <46B0880B.2000009@ru.mvista.com> <46B0AA74.7040100@ru.mvista.com> <46B0B6B4.5090103@ru.mvista.com> <46B0BE52.4000302@ru.mvista.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 16024 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: sshtylyov@ru.mvista.com Precedence: bulk X-list: linux-mips Maciej W. Rozycki wrote: >>> No, I don't. But that was why the original code preferred the wired >>>entry approach over ioremap() -- not to map a whole range... >> Not the only one: dynamic ioremap() seems to be impossible in interrupt >>context. > Well, ioremap() may sleep indeed. So, the only viable option of using sofirq() is mapping all the sparce 2KiB regions at the __init time -- that will waste every half of page though... > How about using a softirq then? Using softirq for what? > Broken hardware (=one that requires PCI configuration accesses from the > IRQ context) is not an excuse to extend the breakage over to software. That's *at least* impractical argument. > Maciej WBR, Sergei