From: "David McIlwraith" <quack@bigpond.net.au>
To: <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.40] DAC960 broken?
Date: Wed, 2 Oct 2002 10:15:57 +1000 [thread overview]
Message-ID: <016101c269a8$e4d85440$0800000a@ValVenus> (raw)
On compiling the driver w/ Dave Olein's patches:
gcc -Wp,-MD,./.DAC960.o.d -D__KERNEL__ -I/usr/src/linux-2.5.40/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-ali
asing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -I/usr/src/
linux-2.5.40/arch/i386/mach-generic -nostdinc -iwithprefix
lude -DKBUILD_BASENAME=DAC960 -c -o DAC960.o DAC960.c
drivers/block/DAC960.c: In function `DAC960_RegisterBlockDevice':
drivers/block/DAC960.c:2112: structure has no member named `major_name'
drivers/block/DAC960.c: In function `DAC960_UnregisterBlockDevice':
drivers/block/DAC960.c:2137: structure has no member named `major_name'
drivers/block/DAC960.c:2150: warning: implicit declaration of function
`blk_clear'
drivers/block/DAC960.c: In function `DAC960_Initialize':
drivers/block/DAC960.c:2766: too many arguments to function `register_disk'
drivers/block/DAC960.c: In function `DAC960_Open':
drivers/block/DAC960.c:5316: too many arguments to function `register_disk'
ld -m elf_i386 -r -o built-in.o elevator.o ll_rw_blk.o blkpg.o genhd.o
block_ioctl.o deadline-iosched.o floppy.o DAC960.o
ld: cannot open DAC960.o: No such file or directory
make[2]: *** [built-in.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.5.40/drivers/block'
make[1]: *** [block] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.40/drivers'
make: *** [drivers] Error 2
Anyone have any ideas?
Thanks in advance,
David McIlwraith mailto:quack@bigpond.net.au
next reply other threads:[~2002-10-01 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 0:15 David McIlwraith [this message]
2002-10-02 1:09 ` [2.5.40] DAC960 broken? Dave Olien
-- strict thread matches above, loose matches on Subject: below --
2002-10-01 23:08 David McIlwraith
2002-10-01 23:19 ` Daniel Phillips
2002-10-02 0:04 ` David McIlwraith
2002-10-02 0:14 ` David McIlwraith
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='016101c269a8$e4d85440$0800000a@ValVenus' \
--to=quack@bigpond.net.au \
--cc=linux-kernel@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 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).