From: Matthew Wilcox <matthew@wil.cx>
To: "David S. Miller" <davem@davemloft.net>
Cc: mroos@linux.ee, sparclinux@vger.kernel.org,
James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
uclinux-v850@lsi.nec.co.jp, rmk@arm.linux.org.uk
Subject: Re: 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd)
Date: Tue, 18 Apr 2006 21:59:08 -0600 [thread overview]
Message-ID: <20060419035908.GH24104@parisc-linux.org> (raw)
In-Reply-To: <20060417.132638.84565849.davem@davemloft.net>
On Mon, Apr 17, 2006 at 01:26:38PM -0700, David S. Miller wrote:
> From: "David S. Miller" <davem@davemloft.net>
> Date: Mon, 17 Apr 2006 13:17:05 -0700 (PDT)
>
> > > Forwarded from linux-scsi.
> > ...
> > > pcibios_resource_to_bus is a new function which is inline in
> > > asm-generic/pci.h. However, sparc64 overrides it as an external
> > > function which is in arch/sparc64/kernel/pci.c, so this looks like some
> > > type of sparc issue.
"new" in the sense of "2 years old"?
2003-03-16 rmk [PCI] pci-8: pci_resource_to_bus()
> > Why does the SYM2 driver possible even need this symbol?
> > That's what I'd like to have explained.
Because the firmware needs to be programmed with the bus address. It's
not unique in this; the Emulex lpfc driver should also be using this
function.
> If you're going to do stuff like this, being that you're the
> first driver to ever make direct usage of this interface,
> please double check the exports on all platforms so that you
> haven't broken the build of the driver as you have on sparc64.
Er, pcmcia was already using it:
./drivers/pcmcia/i82092.c: pcibios_resource_to_bus(sock_info->dev,
®ion, mem->res);
./drivers/pcmcia/yenta_socket.c:
pcibios_resource_to_bus(socket->dev, ®ion, mem->res);
./drivers/pcmcia/yenta_socket.c:
pcibios_resource_to_bus(socket->dev, ®ion, &dev->resource[0]);
I suppose you don't test pci-pcmcia adapters very often on sparc64.
Is there a problem with adding the symbol export? I noticed that v850
also doesn't export that symbol.
next prev parent reply other threads:[~2006-04-19 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOC.4.61.0604171849100.21709@math.ut.ee>
2006-04-17 20:17 ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd) David S. Miller
2006-04-17 20:26 ` David S. Miller
2006-04-19 3:59 ` Matthew Wilcox [this message]
2006-04-19 4:02 ` David S. 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=20060419035908.GH24104@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@SteelEye.com \
--cc=davem@davemloft.net \
--cc=linux-scsi@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=rmk@arm.linux.org.uk \
--cc=sparclinux@vger.kernel.org \
--cc=uclinux-v850@lsi.nec.co.jp \
/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