From: Chris <cb@speedbump.ucs.ualberta.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: i2o & Promise SuperTrak100
Date: 10 Apr 2001 09:19:23 -0600 [thread overview]
Message-ID: <5066gcu6is.fsf@speedbump.ucs.ualberta.ca> (raw)
In-Reply-To: <E14mwEf-00042b-00@the-village.bc.nu>
In-Reply-To: <E14mwEf-00042b-00@the-village.bc.nu>
>>>>> "AC" == Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
>> 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.
AC> I've been talking constructively to promise about the i2o on
AC> the supertrak not working straight off with the kernel i2o
AC> driver. Currently it looks promising
Pun intended? :) Anyways, I too am interested hearing how this
goes. If it isn't going to work out, I'm going to figure out how snip
the PCI line ID'ing it as a RAID. If Promise comes through, then I
don't have to mutilate the card. :)
--
Chris Bayly
Email: Chris.Bayly@UAlberta.CA | CNS, UNIX Support
| 151 General Services Building
| University of Alberta
Web: http://www.ualberta.ca/~cbayly/ | Edmonton, Alberta
| Canada T6G 2S7
next prev parent reply other threads:[~2001-04-10 15:20 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
2001-04-10 11:59 ` Joao Paulo Martins
2001-04-10 15:19 ` Chris [this message]
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=5066gcu6is.fsf@speedbump.ucs.ualberta.ca \
--to=cb@speedbump.ucs.ualberta.ca \
--cc=chris.bayly@ualberta.ca \
--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;
as well as URLs for NNTP newsgroup(s).