From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Joao Paulo Martins <martinsj@lip.pt>, linux-kernel@vger.kernel.org
Subject: Re: i2o & Promise SuperTrak100
Date: Tue, 10 Apr 2001 13:25:12 +0200 [thread overview]
Message-ID: <20010410132512.F493@suse.de> (raw)
In-Reply-To: <20010410092226.M2754@suse.de> <E14mwEf-00042b-00@the-village.bc.nu>
In-Reply-To: <E14mwEf-00042b-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Apr 10, 2001 at 12:22:58PM +0100
On Tue, Apr 10 2001, Alan Cox wrote:
> > > I purchase a Promise SuperTrak100 RAID controler and
> > [snip, SuperTrak not working]
> >
> > I tried talking to Promise recently to get a sample SuperTrak to
> > make this work, but no such luck. So bother Promise and ask what
> > they intend to do about it.
>
> I've been talking constructively to promise about the i2o on the supertrak
> not working straight off with the kernel i2o driver. Currently it looks
> promising
Good, glad someone is having more luck than I. I'd love to see it
work, hence my interest in getting it working.
--
Jens Axboe
next prev parent reply other threads:[~2001-04-10 11:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 13:07 i2o & Promise SuperTrak100 Joao Paulo Martins
2001-04-10 7:22 ` Jens Axboe
2001-04-10 11:22 ` Alan Cox
2001-04-10 11:25 ` Jens Axboe [this message]
2001-04-10 11:59 ` Joao Paulo Martins
2001-04-10 15:19 ` Chris
2001-04-12 18:33 ` Andrew Chan
2001-04-12 19:30 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-02-27 17:14 David Priban
2001-02-27 17:32 ` Alan Cox
2001-02-28 18:26 ` David Priban
2001-02-28 23:10 ` Andrew Morton
2001-03-01 20:40 ` David Priban
2001-02-28 20:11 ` David Priban
2001-02-28 23:38 ` Alan Cox
2001-03-03 17:14 ` David Woodhouse
2001-03-03 17:37 ` Alan Cox
2001-03-01 1:36 ` Jens Axboe
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=20010410132512.F493@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=martinsj@lip.pt \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.