From owner-freebsd-current@FreeBSD.ORG Thu Aug 29 17:09:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C4AC43DE for ; Thu, 29 Aug 2013 17:09:48 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-oa0-f51.google.com (mail-oa0-f51.google.com [209.85.219.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 88B4628DC for ; Thu, 29 Aug 2013 17:09:47 +0000 (UTC) Received: by mail-oa0-f51.google.com with SMTP id h1so956753oag.10 for ; Thu, 29 Aug 2013 10:09:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=SJDQgzFwJfs4GkD0feBRAHCot6kR8PbIW029am1uuZw=; b=RM3aiFQ508rkUw/2GGzl4DhrRETdFDrorFeeUCVjBPkm+Q/BVubA4Ovr7tL2F8Z3uN 0j9/RH5z8Z78m2T0FKqgNHmy/beIYkLIJIcr6d4ig0CT/KzIV4lB4X2ziuxgJQl29Pzh G/rAOOvFWx26Jpito0FBbGr/hDKpWOrJSybjqJs+o8RV0bRKmwvw5sVfOS4c+FUMFzST 5j6U49elW9lfUPp+/Rehs0Sie7wkrHVnVCd38xwqCcQKMLShoslEnRVFeIIN4YJsjQuk maubf+1iJ3Eur7Pg5KLf/B5vzOpBewz1iBSbIp2nyizixLfoTI02XZiO4UaNom6rXSUS lw+w== X-Gm-Message-State: ALoCoQkK8TRH4JGAaAMtAkyMoA2BqZvuW7Rgw/R6O0PS+AcMV5NnoJQ0m2AIrJHZxwXpHLMRCoQq X-Received: by 10.60.52.81 with SMTP id r17mr3360989oeo.3.1377795807801; Thu, 29 Aug 2013 10:03:27 -0700 (PDT) Received: from monkey-bot.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id uz16sm32335159obc.5.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 29 Aug 2013 10:03:27 -0700 (PDT) Sender: Warner Losh Subject: Re: Why are cardbus drivers cbb(4) and pccard(4) still included in GENERIC? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Thu, 29 Aug 2013 11:03:24 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <352C0CD1-909B-445A-A1F4-3942D3A3CE3B@bsdimp.com> References: <201308291054.02641.jhb@freebsd.org> To: Adrian Chadd X-Mailer: Apple Mail (2.1085) Cc: "freebsd-stable@freebsd.org" , Kimmo Paasiala , freebsd-current , freebsd-hardware@freebsd.org, Warner Losh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2013 17:09:48 -0000 On Aug 29, 2013, at 10:14 AM, Adrian Chadd wrote: > .. after tinkering in the USB world, i wonder what's wrong with this: >=20 > * created a basic markup / description language to encapsulate what = PCI/USB probing requires; > * generated both config files _and_ .c / .h files for drivers to = include; > * have the kernel build process do .device_description -> .c/.h (for = compiling) ; devd.conf (for runtime loading); an elf section if you'd = like; and loader-mumble.conf (for loader autoloading.) It is needlessly complex? You seriously don't need 1/10th that = complexity. We've talked about solutions in the past. I even have something that = will automatically do the heavy lifting for compliant drivers (or did = before it decayed). What's needed is for someone to step in and drive it = to completion. Like I said, this has been talked to death at least half a dozen times. Warner