From: Adam Powell <hazelsct@mit.edu>
To: Dan Burcaw <dburcaw@terraplex.com>
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-user@lists.linuxppc.org
Subject: Re: Blue & White G3s
Date: Sat, 24 Apr 1999 22:14:23 -0400 [thread overview]
Message-ID: <37227A7F.9BD5D1C4@mit.edu> (raw)
In-Reply-To: Pine.LNX.3.96.990423165930.19388A-100000@newhope.terraplex.com
Dan Burcaw wrote:
> Folks,
>
> Our in-house development team has successfully ported the CMD646
> driver to the Linux/PPC kernel, offering the much anticipated support
> for the primary ATA chain. This driver supports the ultra-DMA features
> of the chipset, allowing data transfer in excess of 30MB per second.
> The Blue & Whites are now fully functional with ATA, SCSI, and USB.
Er, cool! But I've been using a CMD646 IDE kernel driver since on my AlphaPC
LX164 533 MHz since last October (2.1.116, I believe). Is this your driver,
or have you since reinvented the wheel, or was it Alpha-specific, or am I
missing something?
Zeen,
-Adam "...the firmament sheweth His handywork" (Ps 19:1) ///
............................................................__ ///|
Adam "Cold Fusion" Powell IV Firmament Science & Engineering\\\///_|
http://lyre.mit.edu/~powell/ Standing on the Solid State Rock\XX/ |MIGA
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-04-25 2:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-23 23:02 Blue & White G3s Dan Burcaw
1999-04-25 2:14 ` Adam Powell [this message]
1999-04-25 2:40 ` Dan Burcaw
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=37227A7F.9BD5D1C4@mit.edu \
--to=hazelsct@mit.edu \
--cc=dburcaw@terraplex.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@lists.linuxppc.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).