From: RunNHide <res0g1ta@verizon.net>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11 intio.o build errors
Date: Mon, 15 Dec 2003 22:37:01 -0500 [thread overview]
Message-ID: <3FDE7DDD.2060208@verizon.net> (raw)
In-Reply-To: <20031215113923.GJ23184@fs.tum.de>
On Thu, Dec 11, 2003 at 08:24:40PM -0500, RunNHide wrote:
>> okay - I'm not a n00b but I'm no C programmer or driver developer,
>> either - figured I'd post this - understand there's not a lot of this
>> hardware out there so maybe this will be helpful:
>>
>> CC [M] drivers/scsi/ini9100u.o
>> drivers/scsi/ini9100u.c:111:2: #error Please convert me to
>> Documentation/DMA-mapping.txt
>> drivers/scsi/ini9100u.c:146: warning: initialization from incompatible
>> pointer type
>> drivers/scsi/ini9100u.c:151: warning: initialization from incompatible
>> pointer type
>> drivers/scsi/ini9100u.c:152: warning: initialization from incompatible
>> pointer type
>> drivers/scsi/ini9100u.c: In function `i91uAppendSRBToQueue':
>> drivers/scsi/ini9100u.c:241: error: structure has no member named `next'
>> drivers/scsi/ini9100u.c:246: error: structure has no member named `next'
>> drivers/scsi/ini9100u.c: In function `i91uPopSRBFromQueue':
>> drivers/scsi/ini9100u.c:268: error: structure has no member named `next'
>> drivers/scsi/ini9100u.c:269: error: structure has no member named `next'
>> drivers/scsi/ini9100u.c: In function `i91uBuildSCB':
>> drivers/scsi/ini9100u.c:507: error: structure has no member named `address'
>> drivers/scsi/ini9100u.c:516: error: structure has no member named `address'
>> make[2]: *** [drivers/scsi/ini9100u.o] Error 1
>> make[1]: *** [drivers/scsi] Error 2
>> make: *** [drivers] Error 2
>
>
This is a known problem.
The driver is marked BROKEN in the Kconfig file, and you were only able
to choose it since you said "no" to
Select only drivers expected to compile cleanly
.
Unless someone fixes this driver it will not be available in kernel 2.6.
>> Thanks,
>> RunNHide
>
>
cu
Adrian
--------------------------------------------------------------------------------------
Thanks for the reply - yes, I understand that the code is broken - however, unfortunately, I have one of those initio cards that needs that driver and I would like to be able to use the 2.6 series kernels. Until that driver is fixed, I'll be stuck on 2.4.x kernels.
RunNHide
prev parent reply other threads:[~2003-12-16 3:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 1:24 2.6.0-test11 intio.o build errors RunNHide
2003-12-15 11:39 ` Adrian Bunk
2003-12-16 3:37 ` RunNHide [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=3FDE7DDD.2060208@verizon.net \
--to=res0g1ta@verizon.net \
--cc=bunk@fs.tum.de \
--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