From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Judith Lebzelter <judith@osdl.org>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: Undefined '.bus_to_virt', '.virt_to_bus' causes compile error on Powerpc 64-bit
Date: Tue, 03 Oct 2006 11:05:39 +1000 [thread overview]
Message-ID: <1159837539.5482.15.camel@localhost.localdomain> (raw)
In-Reply-To: <20061002214954.GD665@shell0.pdx.osdl.net>
On Mon, 2006-10-02 at 14:49 -0700, Judith Lebzelter wrote:
> Hello:
>
> For the automated cross-compile builds at OSDL, powerpc 64-bit
> 'allmodconfig' is failing. The warnings/errors below appear in
> the 'modpost' stage of kernel compiles for 2.6.18 and -mm2 kernels.
All those drivers are bogus and need to be updated. They should be
marked CONFIG_BROKEN
Ben.
> Thanks;
> Judith Lebzelter
> OSDL
>
> -----------
>
> Building modules, stage 2.
> MODPOST 1658 modules
> WARNING: Can't handle masks in drivers/ata/ahci:FFFF05
> WARNING: ".virt_to_bus" [sound/oss/sscape.ko] undefined!
> WARNING: ".virt_to_bus" [sound/oss/sound.ko] undefined!
> WARNING: ".bus_to_virt" [sound/oss/cs46xx.ko] undefined!
> WARNING: ".virt_to_bus" [sound/oss/cs46xx.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/scsi/tmscsim.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/scsi/BusLogic.ko] undefined!
> WARNING: ".virt_to_bus" [drivers/net/wan/lmc/lmc.ko] undefined!
> WARNING: ".virt_to_bus" [drivers/message/i2o/i2o_config.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/block/cpqarray.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/atm/zatm.ko] undefined!
> WARNING: ".virt_to_bus" [drivers/atm/zatm.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/atm/horizon.ko] undefined!
> WARNING: ".virt_to_bus" [drivers/atm/firestream.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/atm/firestream.ko] undefined!
> WARNING: ".bus_to_virt" [drivers/atm/ambassador.ko] undefined!
> WARNING: ".virt_to_bus" [drivers/atm/ambassador.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2006-10-03 1:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 21:49 Undefined '.bus_to_virt', '.virt_to_bus' causes compile error on Powerpc 64-bit Judith Lebzelter
2006-10-02 23:44 ` Adrian Bunk
2006-10-03 1:22 ` [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on i386 Adrian Bunk
2006-10-03 1:48 ` Nicholas Miell
2006-10-03 1:58 ` Adrian Bunk
2006-10-03 2:55 ` Nicholas Miell
2006-10-03 4:37 ` Benjamin Herrenschmidt
2006-10-03 11:29 ` Alan Cox
2006-10-03 4:37 ` Benjamin Herrenschmidt
2006-10-03 4:44 ` Andrew Morton
2006-10-03 4:49 ` Benjamin Herrenschmidt
2006-10-03 4:55 ` Andrew Morton
2006-10-03 5:07 ` Adrian Bunk
2006-10-03 9:36 ` Stefan Richter
2006-10-03 11:24 ` Alan Cox
2006-10-03 20:58 ` Undefined '.bus_to_virt', '.virt_to_bus' causes compile error on Powerpc 64-bit Guennadi Liakhovetski
2006-10-03 1:05 ` Benjamin Herrenschmidt [this message]
2006-10-03 11:23 ` Alan Cox
2006-10-03 1:16 ` Paul Mackerras
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=1159837539.5482.15.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=judith@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).