linux-mips
[Top] [All Lists]

Re: Modpost warning on Alchemy

To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Subject: Re: Modpost warning on Alchemy
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Date: Thu, 2 Aug 2007 10:39:21 +0100 (BST)
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
In-reply-to: <46B0BE52.4000302@ru.mvista.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20070801115231.GA20323@linux-mips.org> <46B07B36.1000501@ru.mvista.com> <Pine.LNX.4.64N.0708011337390.20314@blysk.ds.pg.gda.pl> <46B086EB.2030101@ru.mvista.com> <46B0880B.2000009@ru.mvista.com> <Pine.LNX.4.64N.0708011629010.20314@blysk.ds.pg.gda.pl> <46B0AA74.7040100@ru.mvista.com> <Pine.LNX.4.64N.0708011708250.20314@blysk.ds.pg.gda.pl> <46B0B6B4.5090103@ru.mvista.com> <46B0BE52.4000302@ru.mvista.com>
Sender: linux-mips-bounce@linux-mips.org
On Wed, 1 Aug 2007, Sergei Shtylyov 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.  How about using a softirq then?  
Broken hardware (=one that requires PCI configuration accesses from the 
IRQ context) is not an excuse to extend the breakage over to software.

  Maciej

<Prev in Thread] Current Thread [Next in Thread>