From owner-freebsd-arch@FreeBSD.ORG Tue Nov 24 00:56:20 2009 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9689B1065672; Tue, 24 Nov 2009 00:56:20 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.26]) by mx1.freebsd.org (Postfix) with ESMTP id EE0938FC0C; Tue, 24 Nov 2009 00:56:19 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 9so1364042qwb.7 for ; Mon, 23 Nov 2009 16:56:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:x-mailer:mime-version :content-type; bh=C2LBcuGonSWeQ0yrs4v/rtTRH9kG5kbY/KOevrM/Nr0=; b=HvtgnSw8GnxNYb2tMiOdSGzoWt7jEe+JVIRPkvzecvWtJ4+HszQGR6uyUVgKR1Phqc AKtS2+gM99GKpuYvSEfb506bSZ54WskUDSO/wXvZG//QmwN4NT94Y8JZTFy+znMIBixy OjNuaAa8q6Y+7NYQWjXmCUjZRfi+xT3VzR1aM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; b=DuPd3HEAjd7u3BSpSfDnhgYj0DR5BPKHusbILmQHI/S4PbFX41cTia2UZxFIbNfsrg HW3MgzGFuRPa0M4Np5lKwq42J4aPPwVNciG2lDRxDuGb65BEEiTQa9VYNuN3QChlQjgn 5hkGwrDHgwsrqx954E8ybAu/czGu1Vb120nME= Received: by 10.224.33.195 with SMTP id i3mr2826419qad.386.1259024179372; Mon, 23 Nov 2009 16:56:19 -0800 (PST) Received: from kan.dnsalias.net (c-24-91-218-112.hsd1.ma.comcast.net [24.91.218.112]) by mx.google.com with ESMTPS id 5sm10246187qwg.28.2009.11.23.16.56.17 (version=SSLv3 cipher=RC4-MD5); Mon, 23 Nov 2009 16:56:18 -0800 (PST) Date: Mon, 23 Nov 2009 19:56:11 -0500 From: Alexander Kabaev To: freebsd-arch@freebsd.org Message-ID: <20091123195611.150549a0@kan.dnsalias.net> In-Reply-To: <4B0B159B.9040305@FreeBSD.org> References: <4B0B159B.9040305@FreeBSD.org> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/VzI7EKpOBd+8Q+=_pke68rn"; protocol="application/pgp-signature" Cc: Alexander Motin Subject: Re: atausb perspectives X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Nov 2009 00:56:20 -0000 --Sig_/VzI7EKpOBd+8Q+=_pke68rn Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 24 Nov 2009 01:07:07 +0200 Alexander Motin wrote: > Hi. >=20 > At this moment we have two possible ways to support USB mass storages: > umass and atausb. First one handles USB mass storage devices as SCSI > ones by using CAM infrastructure. It is working and maintained. Second > one was made to do the same using ata(4), is reports devices as ATAPI > (in fact the same SCSI). But it is out of build since I can remember. >=20 > Looking on atausb state and ata(4) perspectives generally, I can't > find any reason for having atausb in the tree. What is the public > opinion, can we just drop it now? >=20 > --=20 > Alexander Motin I think the rule is simple and well known: if code rots and nobody steps up as a new maintainer, it gets booted out of the tree. Looks like atausb is firmly in that category. Unless someone raises a hand=20 My $0.02 --=20 Alexander Kabaev --Sig_/VzI7EKpOBd+8Q+=_pke68rn Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iD8DBQFLCy8wQ6z1jMm+XZYRAgNRAJ4iQxhsQWCIoFuVWc3Ban8LzGdUigCbBrh5 k3h5emolxlRr/H84QR8eKRk= =9OmV -----END PGP SIGNATURE----- --Sig_/VzI7EKpOBd+8Q+=_pke68rn--