From: Jack Bowling <jbinpg@shaw.ca>
To: Harald Welte <laforge@gnumonks.org>, lkm <linux-kernel@vger.kernel.org>
Subject: initio scsi won't compile in 2.5.6
Date: Sun, 10 Mar 2002 18:14:57 -0800 [thread overview]
Message-ID: <0GSS00EFLE8W1U@l-daemon> (raw)
In-Reply-To: <20020217173443.H28092@sunbeam.de.gnumonks.org>
In-Reply-To: <3C6F946F.6030207@freesurf.fr> <20020217173443.H28092@sunbeam.de.gnumonks.org>
The following output from an attempted compile of kernel 2.5.6 indicates to me that the initio scsi module has yet to be ported over to the new code. I am not a programmer so am just throwing it out there as something that would be nice to have done if I am eventually ever going to use 2.5.6 and beyond with my scsi hardware :-))
------------
gcc -D__KERNEL__ -I/usr/src/linux-2.5.6/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -DKBUILD_BASENAME=ini9100u -c -o ini9100u.o ini9100u.c
ini9100u.c:111:2: #error Please convert me to Documentation/DMA-mapping.txt
ini9100u.c: In function `i91uBuildSCB':
ini9100u.c:494: structure has no member named `address'
ini9100u.c:503: structure has no member named `address'
make[3]: *** [ini9100u.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.5.6/drivers/scsi'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.5.6/drivers/scsi'
make[1]: *** [_subdir_scsi] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.6/drivers'
make: *** [_dir_drivers] Error 2
-------
jb
PS - please copy me on any replies. I am not subbed to lkml
--
Jack Bowling
mailto: jbinpg@shaw.ca
next prev parent reply other threads:[~2002-03-11 2:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-17 11:30 Kernel 2.4.18-pre9-mjc2 breaks some netfilter modules Kilobug
2002-02-17 16:34 ` Harald Welte
2002-03-11 2:14 ` Jack Bowling [this message]
2002-02-18 18:48 ` Michael Cohen
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=0GSS00EFLE8W1U@l-daemon \
--to=jbinpg@shaw.ca \
--cc=laforge@gnumonks.org \
--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