Subject: Re: OpenBSD's mpi(4)
To: Matt Thomas <firstname.lastname@example.org>
From: Quentin Garnier <email@example.com>
Date: 08/10/2006 09:50:08
Content-Type: text/plain; charset=us-ascii
On Thu, Aug 10, 2006 at 12:20:34AM -0700, Matt Thomas wrote:
> On Aug 10, 2006, at 12:04 AM, Quentin Garnier wrote:
> >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
> siop and esiop support different devices.
> 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.
Quentin Garnier - firstname.lastname@example.org - 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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)
-----END PGP SIGNATURE-----