|| ||"Tom \"spot\" Callaway" <tcallawa-H+wXaHxf7aLQT0dZR+AlfA-AT-public.gmane.org> |
|| ||Eric Paris <eparis-H+wXaHxf7aLQT0dZR+AlfA-AT-public.gmane.org> |
|| ||Re: enable CONFIG_INTEL_TXT |
|| ||Thu, 01 Apr 2010 09:25:59 -0400|
|| ||gcwilson-r/Jw6+rmf7HQT0dZR+AlfA-AT-public.gmane.org, sds-+05T5uksL2qpZYMLLGbcSA-AT-public.gmane.org, kernel-TuqUDEhatI4ANWPb/1PvSmm0pvjS0E/A-AT-public.gmane.org|
|| ||Article, Thread
On 03/31/2010 05:06 PM, Eric Paris wrote:
> what are these binary blobs of which you speak? I thought this was well
> covered. No binary blobs.
As long as you buy certain brand new IBM X-series servers.
For the rest of the x86/x86_64 computing universe, this means binary
blobs, and I think you're fooling yourself if you think that all the
other hardware vendors will be so willing to shove prebuilt code from a
third party into their BIOS (or even have room to do so).
In the non-IBM Xseries case (which is by far, the more common one for
Fedora), we would be enabling this option solely to enable proprietary
binary blobs during the boot process. In my opinion, given that it is
not possible at all for us to troubleshoot or bug fix systems in such a
scenario, we should not imply to our userbase that it is supportable by
enabling this kernel option.
If a user is so motivated to do so, then they're free to build a custom
kernel to enable CONFIG_INTEL_TXT, and it will be even more clear to
them that it is not something they should expect Fedora to support.
to post comments)