From: Mark Watts <m.watts@eris.qinetiq.com>
To: andersen@codepoet.org, Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Promise SATA driver GPL'd
Date: Wed, 23 Jul 2003 14:20:28 +0100 [thread overview]
Message-ID: <200307231420.28717.m.watts@eris.qinetiq.com> (raw)
In-Reply-To: <20030722190705.GA2500@codepoet.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> On Tue Jul 22, 2003 at 02:54:43PM -0400, Jeff Garzik wrote:
> > Bart, Alan, and I have been looking at this. It uses the ancient CAM
> > model, that we don't really want to merge directly in the kernel. It's
> > very close to the libata model, from the user perspective, so life is
> > good.
>
> I was reading over your libata driver yesterday. Certainly a lot
> cleaner than the cam stuff IMHO. Given the info made available
> via the Promise driver, I expect that I could get an initial
> libata host adaptor driver hacked together in short order. After
> all, the Intel one is just 400 lines. So unless you (or anyone
> else) have already started or would prefer to do the honors,
> I'll try to hack something together this evening,
>
> -Erik
Oooh Oooh!!!!
I have an onboard Promise SATA chip - the 30276 (its on an MSI KT4A Ultra
board), which gives me two SATA and one PATA ports (only use 2 at a time)...
If you want someone to test... I can slap a PATA drive onto the PATA port,
but I've been holding off getting any SATA drives until I can use them under
linux, although I'm running out of drive space so this is quite timely... :)
Cheers,
Mark
- --
Mark Watts
Senior Systems Engineer
QinetiQ TIM
St Andrews Road, Malvern
GPG Public Key ID: 455420ED
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/HoucBn4EFUVUIO0RAmwjAJ9/IY3N+AdOdNmfKwPkPoXfDw+PEgCgm7XD
tR56nTVC9b0u8aBZMhWaTag=
=QsVB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-07-23 13:06 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 18:45 Promise SATA driver GPL'd Erik Andersen
2003-07-22 18:54 ` Jeff Garzik
2003-07-22 19:07 ` Erik Andersen
2003-07-22 19:39 ` Samuel Flory
2003-07-22 20:56 ` Jeff Garzik
2003-07-22 21:39 ` Erik Andersen
2003-07-22 23:25 ` Jeff Garzik
2003-08-27 3:01 ` Nick Urbanik
2003-08-27 3:14 ` Jeff Garzik
2003-08-27 9:00 ` Matthias Andree
2003-08-27 11:51 ` Jeff Garzik
2003-07-22 20:57 ` Jeff Garzik
2003-07-23 13:20 ` Mark Watts [this message]
2003-07-23 1:59 ` Andre Hedrick
2003-07-23 2:38 ` Shawn
2003-07-23 10:32 ` Alan Cox
2003-07-23 18:58 ` Andre Hedrick
2003-07-24 11:22 ` Matthias Andree
2003-08-13 13:34 ` Vojtech Pavlik
2003-08-13 14:24 ` Jeff Garzik
2003-08-15 10:17 ` Andre Hedrick
2003-07-25 3:44 ` Milan Roubal
2003-07-23 5:12 Adam J. Richter
2003-07-23 5:28 ` Andre Hedrick
2003-07-23 9:08 ` Adrian Bunk
2003-07-23 10:12 ` Matthias Andree
2003-07-23 10:21 ` Wichert Akkerman
2003-07-23 11:47 ` Alan Cox
2003-07-23 11:54 ` Wichert Akkerman
2003-07-23 10:37 ` Adrian Bunk
2003-07-23 10:29 ` Alan Cox
2003-07-23 10:51 ` Adrian Bunk
2003-07-23 11:43 ` Alan Cox
2003-07-23 12:17 ` Adrian Bunk
2003-07-23 12:32 ` Martin Diehl
2003-07-23 12:57 ` Alan Cox
2003-07-23 19:08 ` Andre Hedrick
2003-07-23 19:19 ` Alan Cox
2003-07-23 19:33 ` Andre Hedrick
2003-07-23 19:46 ` Andre Hedrick
2003-07-23 20:59 ` Roman Zippel
2003-07-23 22:22 ` Andre Hedrick
2003-07-23 22:40 ` Roman Zippel
2003-07-23 22:35 ` Andre Hedrick
2003-07-23 23:02 ` Roman Zippel
2003-07-23 23:08 ` Andre Hedrick
2003-07-23 23:33 ` Roman Zippel
2003-07-23 23:45 ` Andre Hedrick
2003-07-24 0:14 ` dacin
2003-07-24 0:23 ` Andre Hedrick
2003-07-24 0:21 ` David Schwartz
2003-07-24 0:21 ` Andre Hedrick
2003-07-24 13:23 ` Jesse Pollard
2003-07-24 14:01 ` Richard B. Johnson
2003-07-24 18:37 ` David Schwartz
2003-07-23 22:32 ` Andre Hedrick
2003-07-23 22:46 ` Larry McVoy
2003-07-23 23:13 ` Roman Zippel
2003-07-23 10:40 ` Adam Sampson
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=200307231420.28717.m.watts@eris.qinetiq.com \
--to=m.watts@eris.qinetiq.com \
--cc=andersen@codepoet.org \
--cc=jgarzik@pobox.com \
--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).