From: Tom Rini <trini@kernel•crashing.org>
To: Christoph Hellwig <hch@lst•de>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: Missing isa_ symbols
Date: Tue, 3 Feb 2004 16:17:28 -0700 [thread overview]
Message-ID: <20040203231728.GF1860@smtp.west.cox.net> (raw)
In-Reply-To: <20040203210321.GA19689@lst.de>
On Tue, Feb 03, 2004 at 10:03:21PM +0100, Christoph Hellwig wrote:
> I've recently switched CONFIG_ISA on to compile-test various scsi
> drivers and get lots of warnings like:
>
> WARNING: /lib/modules/2.6.2-rc3/kernel/drivers/scsi/wd7000.ko needs unknown symbol isa_bus_to_virt
> WARNING: /lib/modules/2.6.2-rc3/kernel/drivers/scsi/wd7000.ko needs unknown symbol isa_page_to_bus
> WARNING: /lib/modules/2.6.2-rc3/kernel/drivers/scsi/wd7000.ko needs unknown symbol isa_virt_to_bus
> WARNING: /lib/modules/2.6.2-rc3/kernel/drivers/scsi/wd7000.ko needs unknown symbol udelay
>
> from looking at other architectures it looks like architectures
> supporting CONFIG_ISA are supposed to supply them. Any idea how to
> implement this properly for ppc? (and no, I can't test it, by mac
> doesn't actually have an isa bus)
On PPC32, CONFIG_ISA is kinda hack'ish. I know it will / must work on
PRePs, and it _may_ but I'm not certain of some CHRP machines as well.
So you can probably look at the i386 versions of the functions (save for
udelay as Ben mentioned) and do something like:
if (_machine == _MACH_prep) {
... do i386 version ...
} else
return -EINVAL; // whatever
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-03 23:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 21:03 Missing isa_ symbols Christoph Hellwig
2004-02-03 22:25 ` Benjamin Herrenschmidt
2004-02-03 23:17 ` Tom Rini [this message]
2004-02-14 16:46 ` Christoph Hellwig
2004-02-15 10:45 ` Geert Uytterhoeven
2004-02-15 12:24 ` Benjamin Herrenschmidt
2004-02-15 12:25 ` Benjamin Herrenschmidt
2004-02-04 9:40 ` Olaf Hering
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=20040203231728.GF1860@smtp.west.cox.net \
--to=trini@kernel$(echo .)crashing.org \
--cc=hch@lst$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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