mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leon Toh <tltoh@attglobal.net>
To: sflory@rackable.com
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: Tue, 30 Dec 2003 15:46:00 +1100	[thread overview]
Message-ID: <6.0.1.1.2.20031230082335.022d26b0@mail.optusnet.com.au> (raw)
In-Reply-To: <3FF071B1.6010202@rackable.com>

At 05:25 AM 30/12/2003, Samuel Flory wrote:
>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.

Using generic I2O driver is definitely an option for now especially for 
those who wants to immediately jump onto the 2.6 bandwagon. However the 
down site with this is we can't use an of the available Management 
utilities for the card.

Now which is better is not for me to comment on. I shall leave it to others 
to decide for their own as to which is suitable for their environment.

>>>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.

Oh.... I see.

>>>   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.

I can now officially report that the dpt_i2o driver embedded in kernel 
2.6.0 is broken. I'll highlight and bring this up through my contacts back 
at Adaptec. And hopefully we than can get some kind of official resolution 
soon.


  parent reply	other threads:[~2003-12-30  4:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26 23:00 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
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 [this message]
     [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
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=6.0.1.1.2.20031230082335.022d26b0@mail.optusnet.com.au \
    --to=tltoh@attglobal.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sflory@rackable.com \
    /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

all inboxes | Powered by JetHome®