public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Piotr Goczal <bilbo@mazurek.man.lodz.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Promise Fast Track SX6000 i2o driver.
Date: Sun, 22 Aug 2004 15:20:20 +0100	[thread overview]
Message-ID: <1093184419.24617.5.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0408221606520.2571@mazurek.man.lodz.pl>

On Sul, 2004-08-22 at 15:12, Piotr Goczal wrote:
> The Promise driver (distributed via src) is common and is working for both 
> version of firmware.
> 
> So, as I've understood: there will be no working i2o drivers for SX6000 at 
> least to time when Promise publicize documentation to their hardware. 
> :-( Am I right? 

As I understand it the new firmware isn't I2O so I2O would be the wrong
driver anyway. If Promise own source code drivers support it then that
is at least as good as documentation 8). Are promise own drivers for the
sx6000 GPL or not ?

Alan


  reply	other threads:[~2004-08-22 15:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21  9:09 PROBLEM: Promise Fast Track SX6000 i2o driver Piotr Goczal
2004-08-22 11:25 ` Alan Cox
2004-08-22 14:12   ` Piotr Goczal
2004-08-22 14:20     ` Alan Cox [this message]
2004-08-22 16:55       ` Piotr Goczal
2004-08-22 16:21         ` Alan Cox
2004-08-22 17:41           ` Piotr Goczal
2004-08-22 18:48             ` Alan Cox
2004-08-23  0:07               ` Matt Heler
     [not found]               ` <Pine.LNX.4.58.0408230832260.2571@mazurek.man.lodz.pl>
2004-08-23 11:44                 ` Alan Cox
2004-09-09 10:39                   ` Piotr Goczal
2004-11-12  9:05                   ` Piotr Goczal
2004-12-05 11:03                     ` Piotr Goczal

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=1093184419.24617.5.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bilbo@mazurek.man.lodz.pl \
    --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