--0w0yxaBmHk3LBtwQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 10, 2006 at 12:20:34AM -0700, Matt Thomas wrote:
>=20
> On Aug 10, 2006, at 12:04 AM, Quentin Garnier wrote:
>=20
> >On Wed, Aug 09, 2006 at 09:59:10PM -0700, Jason Thorpe wrote:
> >>
> >>On Aug 9, 2006, at 4:31 PM, Quentin Garnier wrote:
> >>
> >>>I have no idea, but my intent certainly isn't to replace mpt(4).
> >>
> >>Well, we shouldn't have TWO drivers for the same chip family...
> >
> >Which one do we kill?  siop or esiop?  de or tlp?  My cvs rm is =20
> >ready...
>=20
> siop and esiop support different devices.
>=20
> tlp doesn't support everything de does.

I was just being facecious.  My point is that unless someone tests
mpi(4) with devices currently supported by mpt(4), we won't know if it
is as suitable as mpt(4) is.  I didn't say I was about to commit it...
Right now I'm making the option available.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"When I find the controls, I'll go where I like, I'll know where I want
to be, but maybe for now I'll stay right here on a silent sea."
KT Tunstall, Silent Sea, Eye to the Telescope, 2004.

--0w0yxaBmHk3LBtwQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iQEVAwUBRNrlMNgoQloHrPnoAQIwZwgAg/hiUsswPH8VP8hTQ/I+iHn/RbMPeTL8
aASadXqrzvF06JOhTTKiIT/F5Tlu+zlQgI5WHF0th5OlT3uYmdDtWWnScF+LVsdJ
It567L/hRS8PPUEN+GDRekY1eEpE+HJ38lpg03KzffHZIOco4CWrzSmCMvfRMKYH
0XZ9ucpLaKINvLTZ2fQRqh4OYsGCCoRXgqb7ZEtfEV9Fh5+Wv+9kdcnf3LNmQFLb
JCJR0gZeFwosSi2REvy2y1RWpAZP1VOufbYDq/8Tu8Lh+hjkZ+YsFhEaemBbWYq+
1e+1sdUXlMLiVS+aNxI0ifJmj3FYbYI0qy76WHb6ISfL4pV31JX48A==
=EKHR
-----END PGP SIGNATURE-----

--0w0yxaBmHk3LBtwQ--