From: Andreas Mohr <andi@lisas•de>
To: Subrata Modak <subrata@linux•vnet.ibm.com>
Cc: linux-net <linux-net@vger•kernel.org>,
Jan-Pascal van Best <janpascal@vanbest•org>,
Andreas Mohr <andi@lisas•de>,
netdev@vger•kernel.org,
Michael Hipp <hippm@informatik•uni-tuebingen.de>,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next <linux-next@vger•kernel.org>,
sachinp <sachinp@linux•vnet.ibm.com>,
linux-kernel <linux-kernel@vger•kernel.org>,
Alexander Beregalov <a.beregalov@gmail•com>,
Linuxppc-dev <Linuxppc-dev@ozlabs•org>
Subject: Re: [BUILD FAILURE 02/12] Next April 21 : PPC64 randconfig [drivers/net/ni65.c]
Date: Wed, 22 Apr 2009 19:20:45 +0200 [thread overview]
Message-ID: <20090422172045.GA10958@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <1240416947.26824.9.camel@subratamodak.linux.ibm.com>
Hi,
On Wed, Apr 22, 2009 at 09:45:47PM +0530, Subrata Modak wrote:
> On Wed, 2009-04-22 at 00:20 +0530, Subrata Modak wrote:
> > I am observing this for the first time:
> >
> > CC drivers/net/ni65.o
> > drivers/net/ni65.c: In function ‘ni65_init_lance’:
> > drivers/net/ni65.c:585: error: implicit declaration of function
> > ‘isa_virt_to_bus’
> > drivers/net/ni65.c: In function ‘ni65_stop_start’:
> > drivers/net/ni65.c:757: error: implicit declaration of function
> > ‘isa_bus_to_virt’
> > make[2]: *** [drivers/net/ni65.o] Error 1
> > make[1]: *** [drivers/net] Error 2
> > make: *** [drivers] Error 2
> > ---
>
> Is there any specific dependency of whether this should be built only
> with certain archs ? As the case may be, i found the functions
> prototypes defined inside the arch specific headers, which definitely
> will not compile on PPC64:
>
> # find . -type f | xargs grep -in isa_virt_to_bus
> ./arch/alpha/include/asm/io.h:119:#define isa_virt_to_bus virt_to_bus
> ./arch/arm/include/asm/io.h:33:#define isa_virt_to_bus virt_to_phys
> ./arch/mips/include/asm/io.h:142:static inline unsigned long
> isa_virt_to_bus(volatile void * address)
> ./arch/parisc/include/asm/io.h:17:static inline unsigned long
> isa_virt_to_bus(void *addr) {
> ./arch/x86/include/asm/floppy.h:182:
> isa_virt_to_bus(addr) >= 0x1000000 ||
> ./arch/x86/include/asm/floppy.h:218: set_dma_addr(FLOPPY_DMA,
> isa_virt_to_bus(addr));
> ./arch/x86/include/asm/io.h:130:static inline unsigned int
> isa_virt_to_bus(volatile void *address)
But NI65 is properly guarded against ISA bus non-support already:
config NI65
tristate "NI6510 support"
depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
help
If you have a network (Ethernet) card of this type, say Y and read
the Ethernet-HOWTO, available from
<http://www.tldp.org/docs.html#howto>.
To compile this driver as a module, choose M here. The module
will be called ni65.
And powerpc _does_ offer ISA bus support:
./arch/powerpc/Kconfig:config ISA
./arch/powerpc/Kconfig: bool "Support for ISA-bus hardware"
./arch/powerpc/Kconfig: Find out whether you have ISA slots on your motherboard. ISA is the
Of course I'm 167% sure that nobody has ever tried those cards on ppc ;-),
but still that would be a _possibility_ that shouldn't be denied straight away.
> Then there should be some solution to the problem inside
> drivers/net/Kconfig
Indeed, which (given my above comments) should probably be to provide
some isa_virt_to_bus() functionality on powerpc or conditionally disable (yuck!)
use of these mechanisms in the drivers.
Anyway, it's certainly not a mistake per se to try to build those drivers on
an ISA-support-enabled powerpc platform.
Of course I'm not certain as to current status of e.g. ni5010, but OTOH I still
have some of those cards... (after all I'm the driver co-author)
Thanks for the heads-up,
Andreas Mohr
prev parent reply other threads:[~2009-04-22 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 18:49 [BUILD FAILURE 02/12] Next April 21 : PPC64 randconfig [drivers/net/ni65.c] Subrata Modak
2009-04-22 16:15 ` Subrata Modak
2009-04-22 17:20 ` Andreas Mohr [this message]
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=20090422172045.GA10958@rhlx01.hs-esslingen.de \
--to=andi@lisas$(echo .)de \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
--cc=a.beregalov@gmail$(echo .)com \
--cc=hippm@informatik$(echo .)uni-tuebingen.de \
--cc=janpascal@vanbest$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-net@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sachinp@linux$(echo .)vnet.ibm.com \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=subrata@linux$(echo .)vnet.ibm.com \
/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