From: Meelis Roos <mroos@linux.ee>
To: sparclinux@vger.kernel.org
Subject: Re: 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus
Date: Mon, 17 Apr 2006 15:49:41 +0000 [thread overview]
Message-ID: <Pine.SOC.4.61.0604171849100.21709@math.ut.ee> (raw)
Forwarded from linux-scsi.
---------- Forwarded message ----------
Date: Mon, 17 Apr 2006 10:30:50 -0400
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-scsi@vger.kernel.org
Subject: Re: 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus
On Mon, 2006-04-17 at 13:22 +0300, Meelis Roos wrote:
> WARNING: /lib/modules/2.6.17-rc1-gc19f7a9e/kernel/drivers/scsi/sym53c8xx_2/sym53c8xx.ko needs unknown symbol pcibios_resource_to_bus
>
> Is is something missing from sparc64, or is sym53c8xx using something
> arch-specific (pcibios sounds like it)?
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.
James
next reply other threads:[~2006-04-17 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 15:49 Meelis Roos [this message]
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:17 ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus David S. Miller
2006-04-17 20:26 ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd) David S. Miller
2006-04-17 20:26 ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus David S. Miller
2006-04-19 3:59 ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus (fwd) Matthew Wilcox
2006-04-19 3:59 ` Matthew Wilcox
2006-04-19 4:02 ` David S. Miller
2006-04-19 4:02 ` 2.6.17-rc1+git, Sym2: unknown symbol pcibios_resource_to_bus David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2006-04-17 10:22 Meelis Roos
2006-04-17 14:30 ` James Bottomley
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=Pine.SOC.4.61.0604171849100.21709@math.ut.ee \
--to=mroos@linux.ee \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.