From owner-freebsd-arch@FreeBSD.ORG Mon Jan 23 23:17:30 2012 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 66B391065670; Mon, 23 Jan 2012 23:17:30 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id EEB5A8FC13; Mon, 23 Jan 2012 23:17:29 +0000 (UTC) Received: from 63.imp.bsdimp.com (63.imp.bsdimp.com [10.0.0.63]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q0NNDo6D086100 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Mon, 23 Jan 2012 16:13:50 -0700 (MST) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <4F1DBB94.900@delphij.net> Date: Mon, 23 Jan 2012 16:13:50 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <0455F6A3-A04A-43C0-9E40-B19ABC4FDDAF@bsdimp.com> References: <20120122201814.GA32081@thorin> <4F1DBB94.900@delphij.net> To: d@delphij.net X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Mon, 23 Jan 2012 16:13:51 -0700 (MST) Cc: Kostik Belousov , Adrian Chadd , freebsd-arch@freebsd.org, Robert Millan Subject: Re: RFC: MK_BLOBS build option 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: Mon, 23 Jan 2012 23:17:30 -0000 I like the idea, but hate the name. BLOB has a negative connotation, = and this option would seem to imply the project doesn't like blobs, = which isn't the case. Can we find a different name for this please? Warner On Jan 23, 2012, at 12:57 PM, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 01/22/12 12:18, Robert Millan wrote: >>=20 >> Hi everyone, >>=20 >> I propose this build option so that users can select if they want >> to disable blobs of binary code in their kernel. Currently Debian >> does this by patching the build system; having a build option would >> make things much easier, but it can also be useful for users whose >> preference is not to install those modules. >>=20 >> Description: >>=20 >> Add MK_BLOBS build option. Setting MK_BLOBS to "no" will disable >> kernel modules that include binary-only blobs of code. >>=20 >> More fine-grained control is provided via MK_BLOBS_HOST (for native >> code that runs on host CPU) and MK_BLOBS_UCODE (for microcode). >>=20 >> Please comment! >=20 > Yes I think that would be good to have. >=20 > Please note that it's still possible to compile these into kernel if > they present in the kernel compile configuration (for instance, device > hptmv), which sounds a little bit non-intuitive to me. Maybe we > should create three include file (BLOBS, BLOBS_HOST, BLOBS_UCODE > perhaps) that lists these modules as 'nodevice ' in the > same time, so they can be included from a kernel configuration file at > the end? >=20 > Cheers, > - --=20 > Xin LI https://www.delphij.net/ > FreeBSD - The Power to Serve! Live free or die > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.18 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >=20 > iEYEARECAAYFAk8du5QACgkQOfuToMruuMD0OwCdFSZe+qzxl2mM70MYdwu73Oo5 > wXoAn0Iy8/hRs3NFThTSKLFYEl3dSQDS > =3D+9aQ > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to = "freebsd-arch-unsubscribe@freebsd.org" >=20 >=20