From: Samuel Flory <sflory@rackable.com>
To: Leon Toh <tltoh@attglobal.net>
Cc: Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Adaptec/DPT I2O Option Omitted From Linux 2.6.0 Kernel Configuration Tool
Date: Mon, 29 Dec 2003 10:25:53 -0800 [thread overview]
Message-ID: <3FF071B1.6010202@rackable.com> (raw)
In-Reply-To: <6.0.1.1.2.20031229201602.021feec0@mail.optusnet.com.au>
Leon Toh wrote:
> At 11:15 AM 29/12/2003, Samuel Flory wrote:
>
>
> How broken is the driver than ? What are the implication's if the driver
> is left as it is for now ?
>
It doesn't compile at all. If it's not fixed your only other option
is the generic i2o driver.
>> It doesn't even compile in 2.4 for a number of archs like amd64.
>
>
> This driver was initially intended only for i386 arch. Furthermore at
> that time when this driver was finalized amd64 wasn't available.
My point is that the driver isn't very portable.
>
>> A while back a bunch of people (including myself) raised the
>> concern through various channels with adaptec. In theroy someone at
>> adaptec is working on it, but there was not an ETA.
>
>
> If you have happen to have a list of issues with this current driver
> together with supporting information to back up those claims, please
> forward them to so that I can escalate those issues into Adaptec via the
> appropriate communication channel. I happen to have a number of
> contact's within Adaptec myself.
>
> By the way I've hack the script file to make Adaptec I2O Option to
> appear in Linux 2.6.0 Kernel Configuration tool. Currently I'm now in
> the middle of recompiling the kernel using current dpti2o driver support
> but haven't got to the dpti2o driver yet.
You might want to hold off on doing a lot of work for a bit. I think
there was a beta driver that was being passed around.
--
There is no such thing as obsolete hardware.
Merely hardware that other people don't want.
(The Second Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-12-29 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 23:00 Adaptec/DPT I2O Option Omitted From Linux 2.6.0 Kernel Configuration Tool Leon Toh
2003-12-29 0:15 ` Samuel Flory
2003-12-29 10:16 ` Leon Toh
2003-12-29 11:40 ` David Lang
2003-12-30 5:15 ` Leon Toh
2003-12-29 18:25 ` Samuel Flory [this message]
2003-12-29 18:32 ` Samuel Flory
2003-12-30 3:32 ` Go Taniguchi
2003-12-30 23:02 ` Samuel Flory
2003-12-30 4:46 ` Leon Toh
[not found] <179fQ-1iK-11@gated-at.bofh.it>
[not found] ` <17TiY-4Pm-19@gated-at.bofh.it>
[not found] ` <182Fy-Lx-15@gated-at.bofh.it>
[not found] ` <18ajG-4Lz-19@gated-at.bofh.it>
[not found] ` <18jZB-4VF-19@gated-at.bofh.it>
2003-12-30 5:19 ` Andi Kleen
2004-01-02 0:08 ` Leon Toh
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 22:42 Leon Toh
[not found] <19aKu-6Z-17@gated-at.bofh.it>
[not found] ` <19aKu-6Z-19@gated-at.bofh.it>
[not found] ` <19aKu-6Z-21@gated-at.bofh.it>
[not found] ` <19aKu-6Z-23@gated-at.bofh.it>
[not found] ` <19aKu-6Z-25@gated-at.bofh.it>
[not found] ` <19aKu-6Z-15@gated-at.bofh.it>
[not found] ` <19lcU-64y-19@gated-at.bofh.it>
2004-01-02 2:02 ` Andi Kleen
2004-01-02 22:36 ` Leon Toh
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=3FF071B1.6010202@rackable.com \
--to=sflory@rackable.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tltoh@attglobal.net \
/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