linux-mips
[Top] [All Lists]

Re: Modpost warning on Alchemy

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: Modpost warning on Alchemy
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Date: Wed, 01 Aug 2007 16:23:18 +0400
Cc: linux-mips@linux-mips.org
In-reply-to: <20070801115231.GA20323@linux-mips.org>
Organization: MontaVista Software Inc.
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20070801115231.GA20323@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.2) Gecko/20040803
Ralf Baechle wrote:

Somebody with a clue on the Alchemy stuff may want to look into this
mostpost warning:

  MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0x1e32dc): Section mismatch: reference to 
.init.text:add_wired_entry (between 'config_access' and 'config_write')
  LD      vmlinux

All the PCI config space accessors on Alchemy will call
arch/mips/pci/ops-au1000.c:config_access which in turn calls add_wired_entry
add_wired_entry in turn is an __init function so it's only a matter of
luck if the PCI code doesn't explode on Alchemy.

So could somebody Alchemist try to rewrite this to use ioremap() instead?

   Will ioremap() work for 4 GB range? I guess not.
What actually needs to be done is move this code under if (first_cfg) into __init function...

Thanks,

  Ralf

MBR, Sergei

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