Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 23 Jan 2012 16:13:50 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        d@delphij.net
Cc:        Kostik Belousov <kostikbel@gmail.com>, Adrian Chadd <adrian@freebsd.org>, freebsd-arch@freebsd.org, Robert Millan <rmh@freebsd.org>
Subject:   Re: RFC: MK_BLOBS build option
Message-ID:  <0455F6A3-A04A-43C0-9E40-B19ABC4FDDAF@bsdimp.com>
In-Reply-To: <4F1DBB94.900@delphij.net>
References:  <20120122201814.GA32081@thorin> <4F1DBB94.900@delphij.net>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <device name>' in the
> same time, so they can be included from a kernel configuration file at
> the end?
>=20
> Cheers,
> - --=20
> Xin LI <delphij@delphij.net>	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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0455F6A3-A04A-43C0-9E40-B19ABC4FDDAF>